Re: Functions and transactions - Mailing list pgsql-admin

From Tom Lane
Subject Re: Functions and transactions
Date
Msg-id 4363.1110567273@sss.pgh.pa.us
Whole thread Raw
In response to Re: Functions and transactions  (Kris Kiger <kris@musicrebellion.com>)
List pgsql-admin
Kris Kiger <kris@musicrebellion.com> writes:
> Interesting.  That makes sense, though.  So, is there a good way to lock
> a set of rows using SELECT FOR UPDATE in plpgsql?  I assume using
> PERFORM would yield the same problem, because it immediately discards
> the results.

I think PERFORM would work.  The fact that plpgsql ignores the results
doesn't mean you don't have lock on the rows.

            regards, tom lane

pgsql-admin by date:

Previous
From: Adrian Nida
Date:
Subject: Re: [HACKERS] PostgreSQL pam ldap document
Next
From: Dick Davies
Date:
Subject: Re: [HACKERS] PostgreSQL pam ldap document