Re: Final /contrib cleanup -- yes/no?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Final /contrib cleanup -- yes/no?
Date: 2008-11-06 22:00:55
Message-ID: 15875.1226008855@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus <josh(at)agliodbs(dot)com> writes:
> 1) Take the "SET search_path=public" out of all contrib SQL scripts so
> that DBAs can determine the correct schema by using PGOPTIONS.

I don't recall that having been proposed, and I don't think it's really
a good idea. We intentionally put those SETs in, not that long ago.

> 2) Add BEGIN/COMMIT to all SQL scripts.

The effects of that haven't been debated, either. Are you sure none of
those scripts rely on surviving errors? What about the possibility of
other scripts including them when already inside a BEGIN block?

The thing we really need to make that stuff nice is a proper module
facility. Changing stuff at the margins in the meantime doesn't really
do much except create more different possible behaviors that people will
have to deal with.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2008-11-06 22:13:09 Re: Final /contrib cleanup -- yes/no?
Previous Message Josh Berkus 2008-11-06 21:48:12 Final /contrib cleanup -- yes/no?