Re: Edge case problem with pg_dump - Mailing list pgsql-hackers

From Brent Verner
Subject Re: Edge case problem with pg_dump
Date
Msg-id 20020525220534.GB416@rcfile.org
Whole thread Raw
In response to Re: Edge case problem with pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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


pgsql-hackers by date:

Previous
From: Brent Verner
Date:
Subject: Re: Edge case problem with pg_dump
Next
From: Bruce Momjian
Date:
Subject: Re: Temp tables are curious creatures....