pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael McCarthy <michael@tcsi.com>
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] key set delete query
Date: Fri, 14 Jan 2000 10:02:33 -0500
Message-ID: <29298.947862153@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.GSO.3.96.1000113235142.2456A-100000@sanmarino.tcsi.com>
References: <Pine.GSO.3.96.1000113235142.2456A-100000@sanmarino.tcsi.com>

Michael McCarthy <michael@tcsi.com> writes:
> I notice to my dismay that key set query optimization only works for
> SELECT :( This could be a significant performance problem for my
> application, which would like to do a key set based delete.

> Any thoughts on the advisability of changing the criteria for
> transformation of key set based queries?

I have no intention of putting any effort into KSQO, other than
removing it as soon as the rest of the optimizer does a reasonable
job with OR queries ;-).  You could try removing the check for a
SELECT and see what happens, though.

> I know that cnfify is being reworked for release 7; any comment on when
> 7 will be available?

Current plan is to go to beta mode on 1 Feb.  Final release, hard to
say.  Marc will probably say "1 March for sure", but I lean more towards
the "when it's ready" approach...

> How stable is the latest beta? About 10 days ago I tried building from the
> daily snapshot, but didn't get very far.

We seem to be in the usual pre-beta flurry of committing half-tested
code :-(.  I think the underlying stability of the system has been
amazingly good throughout this development cycle, but there have been
a lot of minor build and regress test problems in the past couple weeks.
If you have the know-how to get past those, things pretty much work.

			regards, tom lane



view thread (2+ messages)

Message-ID: <29298.947862153@sss.pgh.pa.us>
Permalink:  ../29298.947862153@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/29298.947862153@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, michael@tcsi.com
  Subject: Re: [SQL] key set delete query
  In-Reply-To: <29298.947862153@sss.pgh.pa.us>
  References: <Pine.GSO.3.96.1000113235142.2456A-100000@sanmarino.tcsi.com> <29298.947862153@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox