Samuel Tardieu <[EMAIL PROTECTED]> writes:
>>> Do I have the guarantee that, in any event, rows deleted from
>>> table t by the delete won't reappear in the select result?
>>
>> i do not think you have that guarantee in READ COMMITTED mode
>> because there is a slight possibility another backend s
> "Chester" == Chester Kustarz <[EMAIL PROTECTED]> writes:
> On Wed, 28 Jan 2004, Chester Kustarz wrote:
>> On Wed, 28 Jan 2004, Samuel Tardieu wrote: > If in a transaction I
>> call an embedded function in Pl/PgSQL, in which > I have:
>> >
>> > delete from t where condition; > for e in select
On Wed, 28 Jan 2004, Chester Kustarz wrote:
> On Wed, 28 Jan 2004, Samuel Tardieu wrote:
> > If in a transaction I call an embedded function in Pl/PgSQL, in which
> > I have:
> >
> > delete from t where condition;
> > for e in select distinct on (f) * from t where ... loop
> > ...
> > en
On Wed, 28 Jan 2004, Samuel Tardieu wrote:
> If in a transaction I call an embedded function in Pl/PgSQL, in which
> I have:
>
> delete from t where condition;
> for e in select distinct on (f) * from t where ... loop
> ...
> end loop;
>
> Do I have the guarantee that, in any event, rows
If in a transaction I call an embedded function in Pl/PgSQL, in which
I have:
delete from t where condition;
for e in select distinct on (f) * from t where ... loop
...
end loop;
Do I have the guarantee that, in any event, rows deleted from table t
by the delete won't reappear in the s
