| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Joshua Ma <josh(at)benchling(dot)com>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>, Victor Pontis <victor(at)benchling(dot)com> |
| Subject: | Re: pg_restore casts check constraints differently |
| Date: | 2016-03-30 02:40:46 |
| Message-ID: | 10332.1459305646@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Tue, Mar 29, 2016 at 2:45 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> It's not really different. What you're seeing is pg_dump (or actually
>> ruleutils.c) choosing to dump some implicit casts explicitly to ensure
>> that the expression is parsed the same way next time.
> Why don't we just use ruleutils.c to generate \d results so that what we
> end up showing is canonical?
We do. AFAIK, what psql's \d shows in these cases is the same as what
pg_dump will print. Joshua's complaint is that it isn't necessarily
identical to what was input.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2016-03-30 02:56:16 | Re: pg_restore casts check constraints differently |
| Previous Message | Adrian Klaver | 2016-03-29 22:51:37 | Re: debugging server connection issue |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-03-30 02:43:46 | Re: Please correct/improve wiki page about abbreviated keys bug |
| Previous Message | Tom Lane | 2016-03-30 02:31:54 | Re: Please correct/improve wiki page about abbreviated keys bug |