| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | Andy Kriger <akriger(at)greaterthanone(dot)com> |
| Cc: | Pgsql-General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: lock table question |
| Date: | 2002-12-30 23:58:30 |
| Message-ID: | Pine.LNX.4.33.0212301657440.5862-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 30 Dec 2002, Andy Kriger wrote:
> It doesn't lock the row from being read. I want to make sure the row cannot
> be read until I have done my read and updated if necessary. LOCK TABLE does
> that but also prevents other rows from being read which is a bit overzealous
> for my taste (the app is small so it's probably not a big deal in this case,
> but I can see in future possibilities how it would be).
You do realize of course, that with MVCC and serializable transactions,
the readers can't see what you're writing. i.e. they won't see any of
your changes until a commit.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nigel J. Andrews | 2002-12-30 23:59:18 | Re: pg and transactions |
| Previous Message | Tommi Mäkitalo | 2002-12-30 23:25:51 | new c++-interface for postgresql |