On Mon, 2008-01-28 at 09:21 +, Dean Rasheed wrote:
This is the patch allows logging of the explain plan for each query run, as
described here:
http://archives.postgresql.org/pgsql-performance/2008-01/msg00245.php
I hope this is useful.
This looks very good, though I don't think its
On Sat, 2008-03-29 at 08:47 +, Dean Rasheed wrote:
I also think we should only log the EXPLAIN if we have logged the SQL
statement. It's not much use on its own anyway. This then allows this
feature to work neatly with log_statement and
log_min_duration_statement.
Wouldn't that
Andreas 'ads' Scherbaum wrote:
The attached patch for HEAD extends the CREATE LANGUAGE statement by an
IF NOT EXISTS option which in effect changes the raised error into a
notice.
Before i continue working on this patch i would like to know if this
extension has a chance to go into PG and what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Feb 23, 2008 at 01:13:38PM +0100, Mathias Hasselmann wrote:
[...]
Avahi/Bonjour/DNS-SD support[1] is very important, for integrating
Postgresql with modern desktop environments like OSX, GNOME, KDE: It's
very convenient to choose active
Heikki Linnakangas wrote:
Andreas 'ads' Scherbaum wrote:
The attached patch for HEAD extends the CREATE LANGUAGE statement by an
IF NOT EXISTS option which in effect changes the raised error into a
notice.
Before i continue working on this patch i would like to know if this
extension has a
Andrew Dunstan [EMAIL PROTECTED] writes:
Heikki Linnakangas wrote:
The way we've solved this problem for other CREATE commands is to add
OR REPLACE option, instead of IF NOT EXISTS. We should do the same
here.
My recollection is that we only do that where we need to for reasons of
Heikki Linnakangas [EMAIL PROTECTED] writes:
The way we've solved this problem for other CREATE commands is to add
OR REPLACE option, instead of IF NOT EXISTS. We should do the same here.
If we're willing to consider a solution that is specific to CREATE
LANGUAGE (as opposed to implementing IF
Tom Lane wrote:
Heikki Linnakangas [EMAIL PROTECTED] writes:
The way we've solved this problem for other CREATE commands is to add
OR REPLACE option, instead of IF NOT EXISTS. We should do the same here.
If we're willing to consider a solution that is specific to CREATE
LANGUAGE (as opposed
Greg Sabino Mullane [EMAIL PROTECTED] writes:
Full support for all schema and table name combinations when
getting a list of attributes. All of the following will now work:
select * from information_schema.columns where tab
select * from foo where tab
select * from user where tab
select *
Heikki Linnakangas wrote:
Tom Lane wrote:
Heikki Linnakangas [EMAIL PROTECTED] writes:
The way we've solved this problem for other CREATE commands is to
add OR REPLACE option, instead of IF NOT EXISTS. We should do
the same here.
If we're willing to consider a solution that is
Magnus Hagander [EMAIL PROTECTED] writes:
If we're implementing IF NOT EXISTS across the board, let's do that for
languages at the same time as for others.
Yeah, if we were going to do it at all it should be handled
across-the-board, the way DROP IF EXISTS was. However, I seem to recall
that
Tom Lane wrote:
Magnus Hagander [EMAIL PROTECTED] writes:
If we're implementing IF NOT EXISTS across the board, let's do that
for languages at the same time as for others.
Yeah, if we were going to do it at all it should be handled
across-the-board, the way DROP IF EXISTS was. However, I
On Tue, 2008-03-25 at 12:54 -0700, Neil Conway wrote:
Barring any objections, I'll apply this to HEAD tomorrow.
Applied to HEAD.
-Neil
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
13 matches
Mail list logo
