Re: PL/pgSQL bug?

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: JanWieck(at)Yahoo(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: PL/pgSQL bug?
Date: 2001-08-12 01:48:05
Message-ID: 20010812104805Q.t-ishii@sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> > Ok, maybe another workaround might be adding a checking for cmax in
> > the subselect:
>
> > SELECT INTO myid i FROM t1 WHERE i = (SELECT i FROM t1 WHERE i = 1);
>
> > to make sure that cmax > 0?
>
> Huh? How would that help?

According to the doc, tuples with cmax > 0 should not be visible to
the current transaction, no?
--
Tatsuo Ishii

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-08-12 01:58:35 Re: Re: [PATCHES] Select parser at runtime
Previous Message Peter Eisentraut 2001-08-12 00:26:51 Re: [PATCHES] Select parser at runtime