154 Commits (44fbe20d620d4f2e39aaa9896de4683e55b0d317)

Author	SHA1	Message	Date
Marc G. Fournier	208a30f23d	The patch does several things: ... It adds a WITH OIDS option to the copy command, which allows dumping and loading of oids. If a copy command tried to load in an oid that is greater than its current system max oid, the system max oid is incremented. No checking is done to see if other backends are running and have cached oids. pg_dump as its first step when using the -o (oid) option, will copy in a dummy row to set the system max oid value so as rows are loaded in, they are certain to be lower than the system oid. pg_dump now creates indexes at the end to speed loading Submitted by: Bruce Momjian <maillist@candle.pha.pa.us>	29 years ago
Marc G. Fournier	e7a110b418	This patch can be installed as part of 1.02.1 so people can properly ... pg_dump and load to 2.0. I haven't gotten any feedback on whether people want it, so I am submitting it for others to decide. I would recommend an install in 1.02.1. I had said that the 2.0 pg_dump could dump a 1.02.1 database, but I was wrong. The copy is actually performed by the backend, and the 2.0 database will not be able to read 1.02.1 databases because of the new system columns. This patch does several things. It copies nulls out as \N, so they can be distinguished from '' strings. It fixes a problem where backslashes in the input stream were not output as double-backslashes. Without this patch, backslashes copied out were deleted upon input, or interpreted as special characters. Third, input is now terminated by backslash-period. This can not be part of a normal input stream. I tested this by creating a database with all sorts of nulls, backslash, and period fields and dumped the database and reloaded into a new database and compared them. Submitted by: Bruce	30 years ago
Marc G. Fournier	7344d69898	Finished merging in src/backend from Dr. George's source tree	30 years ago
Marc G. Fournier	d31084e9d1	Postgres95 1.01 Distribution - Virgin Sources	30 years ago