| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: sorting operators in pg_dump |
| Date: | 2012-01-03 17:54:27 |
| Message-ID: | CA+TgmoYMGrkanBLxakm6noTgPpbmqDuL0diVPHvjp10BBG+M4g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jan 1, 2012 at 11:50 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> Currently, pg_dump sorts operators by name, but operators with the same
> name come out in random order. A few releases ago we adjusted this for
> functions, so that they are in increasing number of arguments order.
> I'd like to do this for operators as well, so that they come out in
> order, say, prefix, postfix, infix.
>
> (It might be surprising that something like this is necessary, but it
> happens. ip4r for example contains operators with different fixnesses
> (fixities?).)
>
> Patch attached, and a little test case.
Seems like a good idea. The patch looks good, too.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-01-03 17:55:58 | Re: ALTER TABLE lock strength reduction patch is unsafe |
| Previous Message | Robert Haas | 2012-01-03 17:39:16 | Re: ALTER TABLE lock strength reduction patch is unsafe |