From: | "Edward Q(dot) Bridges" <ed(dot)bridges(at)buzznik(dot)com> |
---|---|
To: | "PostgreSQL general mailing list" <pgsql-general(at)postgresql(dot)org>, "Roger Wernersson" <roger(dot)wernersson(at)mindark(dot)com> |
Subject: | RE: Re: Unanswered questions about Postgre |
Date: | 2000-12-12 16:10:09 |
Message-ID: | 200012121657.eBCGvem05954@mail.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 12 Dec 2000 12:04:46 +0100, Roger Wernersson wrote:
>
> I can't BEGIN - SELECT FOR UPDATE - INSERT or UPDATE - COMMIT as someone
> might insert after my SELECT and before my INSERT.
>
correct me if i'm wrong, but a select for update locks the table for
an insert or an update until the end of the transaction.
--e--
> Is there a right solution?
>
> /Roger
>
> -----Original Message-----
> From: Tim Kientzle [mailto:kientzle(at)acm(dot)org]
> Sent: den 12 december 2000 02:10
> To: PostgreSQL general mailing list
> Subject: [GENERAL] Re: Unanswered questions about Postgre
>
>
> > Of course, people really shouldn't be inserting
> > objects which already exist, ...
>
> On the contrary, the best way to test if
> something already exists is to just try the
> INSERT and let the database tell you if
> it's already there. Both faster and more
> reliable than doing SELECT then INSERT.
>
> - Tim
>
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Heaven | 2000-12-12 16:36:10 | COPY doesnt work on views |
Previous Message | Edward Q. Bridges | 2000-12-12 16:08:09 | Re: manuals |