11 Commits

Author	SHA1	Message	Date
Tom Lane	0e9b05bde9	expected results for dblink test seem to be out of date ...	2003-09-14 02:30:07 +00:00
Tom Lane	8fd5b3ed67	Error message editing in contrib (mostly by Joe Conway --- thanks Joe!)	2003-07-24 17:52:50 +00:00
Bruce Momjian	8f337e86cd	Please apply attached patch to contrib/dblink. It adds named persistent ... connections to dblink. Shridhar Daithanka	2003-06-25 01:10:15 +00:00
Tom Lane	f85f43dfb5	Backend support for autocommit removed, per recent discussions. The ... only remnant of this failed experiment is that the server will take SET AUTOCOMMIT TO ON. Still TODO: provide some client-side autocommit logic in libpq.	2003-05-14 03:26:03 +00:00
Tom Lane	11d337185d	Fix inappropriate quoting in dblink. From Joe Conway.	2002-11-23 18:59:25 +00:00
Tom Lane	bfccacf3f8	Fix dblink regression test so that it works when repeated: don't ... create a second database, just loop back to 'regression'. Patch from Joe Conway 10/22/02.	2002-11-03 04:52:09 +00:00
Bruce Momjian	e5cf1a8a26	SET autocommit no longer needed in /contrib because pg_regress.sh does ... it automatically now on regression session startup.	2002-10-21 01:42:14 +00:00
Bruce Momjian	5214f09b27	Clean up for dblink autocommit OFF handling.	2002-10-18 19:11:27 +00:00
Bruce Momjian	aa4c702eac	Update /contrib for "autocommit TO 'on'". ... Create objects in public schema. Make spacing/capitalization consistent. Remove transaction block use for object creation. Remove unneeded function GRANTs.	2002-10-18 18:41:22 +00:00
Tom Lane	cd7a3b6c0d	Simplify handling of second database for dblink tests.	2002-09-14 22:00:59 +00:00
Tom Lane	d724c314da	The attached adds GRANTs to PUBLIC for dblink functions, removes the ... non-standard regression test, and adds standard installcheck regression test support. The test creates a second database (regression_slave) and drops it again, in order to avoid the cheesy-ness of connecting back to the same database ;-) Joe Conway	2002-09-14 20:28:54 +00:00