I just found out that datestyle affects the output of COPY, and hence
pg_dump:

	test=> create table test(x date);
	CREATE	
	test=> insert into test values ('2001-07-31');
	INSERT 17239 1
	test=> set datestyle to 'postgres, dmy';
	SET
	test=> copy test to '/tmp/x';
	COPY
	test=> \!cat /tmp/x
	31-07-2001
	test=> set datestyle to 'postgres, mdy';
	SET
	test=> copy test to '/tmp/x';
	COPY
	test=> \!cat /tmp/x
	07-31-2001

Should we set the datestyle at the top of pg_dump files like we do with
encoding and other settings?   Seems we should.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

Thu, 15 Apr 2004 00:43:08 -0400 (EDT)
Bruce Momjian <pgman@candle.pha.pa.us>
Problem with COPY and DateStyle
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Should we set the datestyle at the top of pg_dump files like we do with
> encoding and other settings?   Seems we should.

That was dealt with quite a while back.

			regards, tom lane

Thu, 15 Apr 2004 01:28:58 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: Problem with COPY and DateStyle 