From: | Pavel Golub <pavel(at)microolap(dot)com> |
---|---|
To: | cpacejo(at)clearskydata(dot)com, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #14064: Sort order of bytea, etc. not defined |
Date: | 2016-05-04 06:16:46 |
Message-ID: | 1403837265.20160504091646@gf.microolap.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hello, Cpacejo.
You wrote:
ccc> The following bug has been logged on the website:
ccc> Bug reference: 14064
ccc> Logged by: Chris Pacejo
ccc> Email address: cpacejo(at)clearskydata(dot)com
ccc> PostgreSQL version: 9.5.2
ccc> Operating system: any
ccc> Description:
ccc> The documentation does not define (nor call out as undefined) the sort order
ccc> of bytea, bit varying, and other sequence types. While the bytea sort order
ccc> is unsurprising (a < b if a is a prefix of b, but b > a if a prefix of b >
ccc> the same length prefix of a), it is not the only such "unsurprising" sort
ccc> order, and it would be helpful to have the guarantee that this sort order
ccc> can be relied upon (especially in concert with range types).
You shouls use explicit type casting for such types.
--
With best wishes,
Pavel mailto:pavel(at)gf(dot)microolap(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | wangyong20009109 | 2016-05-04 07:26:36 | BUG #14125: when master set tablespace,slave recovery xlog pending |
Previous Message | Fabien COELHO | 2016-05-04 05:46:42 | Re: [BUGS] Breakage with VACUUM ANALYSE + partitions |