Re: Current initdb broken.

[ Charset ISO-8859-1 unsupported, converting... ]
> Um, excuse me. Any changes to the format of pg_shadow will break
> pg_dumpall, therefore this needs to be hold back until next release.
>

Woo, hoo. We have triggers and constraints on COPY. We could do the
default values that way. Seems DEFAULT is not activated in COPY. I
knew there was some limitation in COPY.

test=> create table test(x int, y int default 5);
CREATE
test=> copy test from '/tmp/x';
COPY
test=> select * from test;
x | y
---+---
1 |
(1 row)

Can someone suggest a clean solution for COPY? Seems we have triggers
and constraints.

--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026