Re: Edge case problem with pg_dump

From: Brent Verner <brent(at)rcfile(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Philip Warner <pjw(at)rhyme(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Edge case problem with pg_dump
Date: 2002-05-25 22:05:34
Message-ID: 20020525220534.GB416@rcfile.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

[2002-05-25 11:44] Tom Lane said:
| > In your responses you also raised the problem of COPY having to know about
| > default values for columns if we allow subsets of columns when we load
| > data; does that mean that COPY does something more fancy than the
| > equivalent of an INSERT?
|
| No, but it would have to be equivalent to an INSERT. BTW, the
| default-value mechanism is cleaner than it used to be and so this
| doesn't seem like as serious an objection anymore. Since COPY already
| has to have enough mechanism to evaluate constraint expressions,
| evaluating defaults too doesn't seem that horrid.

The last version of the COPY (attlist) patch does use column defaults.
Again, I'll try to get this cleaned up over this (long) weekend.

b

--
"Develop your talent, man, and leave the world something. Records are
really gifts from people. To think that an artist would love you enough
to share his music with anyone is a beautiful thing." -- Duane Allman

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-05-25 22:43:59 Re: Temp tables are curious creatures....
Previous Message Brent Verner 2002-05-25 22:00:58 Re: Edge case problem with pg_dump