From: Tom Lane <tgl@sss.pgh.pa.us>
To: Paul McGarry <paulm@opentec.com.au>
Cc: pgsql-sql@postgresql.org
Subject: Re: MAX() of 0 records.
Date: Thu, 06 Jul 2000 23:29:42 -0400
Message-ID: <8477.962940582@sss.pgh.pa.us> (raw)
In-Reply-To: <396535EF.8132CF80@opentec.com.au>
References: <396535EF.8132CF80@opentec.com.au>
Paul McGarry <paulm@opentec.com.au> writes:
> However there will be situations where there are no records for
> a given item_entry_id with item_live='t'. Currently when I try
> do update/insert a record so that this occurs I get the following
> error 'ERROR: ExecutePlan: (junk) 'ctid' is NULL!' and the
> insert/update attempt is rolled back.
This seems like a backend bug to me, but being an overworked hacker
I'm too lazy to try to reconstruct the scenario from your sketch.
Could I trouble you to submit a formal bug report with a specific,
hopefully compact script that triggers the problem?
> Is there a good way of going about this or should I just be wrapping
> the whole thing up in an
Until I've isolated the bug I don't want to speculate about whether
it'll be reasonable to try to back-patch a fix into 7.0.*. Usually
we don't risk back-patching complex fixes into stable releases, but
the fix might be simple once we know the cause.
regards, tom lane
PS: I trust you're using 7.0.* ?
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, paulm@opentec.com.au
Subject: Re: MAX() of 0 records.
In-Reply-To: <8477.962940582@sss.pgh.pa.us>
References: <396535EF.8132CF80@opentec.com.au> <8477.962940582@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