| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Keith Fiske <keith(at)omniti(dot)com>, "Daniel O'Connor" <darius(at)dons(dot)net(dot)au>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] BUG #9652: inet types don't support min/max |
| Date: | 2014-06-03 14:24:46 |
| Message-ID: | 12477.1401805486@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> I didn't reall look at the patch, but it very much looks to me like that
> query result could use the \a\t treatment that rules.sql and
> sanity_check.sql got. It's hard to see the actual difference
> before/after the patch.
> I'll patch that now, to reduce the likelihood of changes there causing
> conflicts for more people.
Personally, I would wonder why the regression tests contain such a query
in the first place. It seems like nothing but a major maintenance PITA.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-06-03 14:27:33 | Re: [BUGS] BUG #9652: inet types don't support min/max |
| Previous Message | Andres Freund | 2014-06-03 09:51:39 | Re: [BUGS] BUG #9652: inet types don't support min/max |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-06-03 14:27:33 | Re: [BUGS] BUG #9652: inet types don't support min/max |
| Previous Message | Fujii Masao | 2014-06-03 14:19:37 | pg_basebackup failed to back up large file |