| From: | cpacejo(at)clearskydata(dot)com |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #14064: Sort order of bytea, etc. not defined |
| Date: | 2016-04-04 20:33:04 |
| Message-ID: | 20160404203304.15198.54263@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 14064
Logged by: Chris Pacejo
Email address: cpacejo(at)clearskydata(dot)com
PostgreSQL version: 9.5.2
Operating system: any
Description:
The documentation does not define (nor call out as undefined) the sort order
of bytea, bit varying, and other sequence types. While the bytea sort order
is unsurprising (a < b if a is a prefix of b, but b > a if a prefix of b >
the same length prefix of a), it is not the only such "unsurprising" sort
order, and it would be helpful to have the guarantee that this sort order
can be relied upon (especially in concert with range types).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-04-04 20:46:19 | Re: BUG #13970: Vacuum hangs on particular table; cannot be terminated - requires `kill -QUIT pid` |
| Previous Message | Tom Lane | 2016-04-04 19:56:37 | Re: BUG #14062: pg_dump dies after dumping first 60 gigabytes of text for large table |