From: Troels Arvin <troels@arvin.dk>
To: pgsql-sql@postgresql.org
Subject: Re: Nested Sets
Date: Sat, 16 Apr 2005 22:02:24 +0200
Message-ID: <pan.2005.04.16.20.02.24.212579@arvin.dk> (raw)
References: <fc63e1af0504160531795a314d@mail.gmail.com>
<pan.2005.04.16.13.04.47.372088@arvin.dk>
<fc63e1af05041607286c0447e8@mail.gmail.com>
<20050416181457.GA14377@phlogiston.dyndns.org>
On Sat, 16 Apr 2005 14:14:57 -0400, Andrew Sullivan wrote:
> You shouldn't need to do anything special around table
> locking.
- Except of one wants "True Serializability" (see chapter 12.2 in the
manual). But I don't know if it's possible to handle table locking from
within a user defined function.
--
Greetings from Troels Arvin, Copenhagen, Denmark
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: troels@arvin.dk
Subject: Re: Nested Sets
In-Reply-To: <pan.2005.04.16.20.02.24.212579@arvin.dk>
* 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