From: Joseph Shraibman <jks@p1.selectacast.net>
To: Thomas Lockhart <lockhart@alumni.caltech.edu>
Cc: dougt@mugc.cc.monash.edu.au
Cc: tgl@sss.pgh.pa.us
Cc: gary.stainburn@ringways.co.uk
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] locking on database updates
Date: Tue, 07 Dec 1999 14:36:16 -0500
Message-ID: <384D61B0.9311FFC5@selectacast.net> (raw)
References: <199912070358.OAA26398@mugca.cc.monash.edu.au>
<384C8A41.F168EF9D@selectacast.net>
<384C9404.995238C0@alumni.caltech.edu>
Thomas Lockhart wrote:
> > Thanks. I just wish the postgres documentation were a little better.
>
> Um, if you were a bit more specific that would be helpful ;)
>
> The topic you have asked about is in the docs somewhere; now that you
>
So it is. I was looking under 'tutorial' and it was in 'postgres'
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-interfaces@postgresql.org
Cc: jks@p1.selectacast.net, lockhart@alumni.caltech.edu, dougt@mugc.cc.monash.edu.au, tgl@sss.pgh.pa.us, gary.stainburn@ringways.co.uk
Subject: Re: [INTERFACES] locking on database updates
In-Reply-To: <384D61B0.9311FFC5@selectacast.net>
* 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