| From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | "Dennis Brakhane" <brakhane(at)googlemail(dot)com> |
| Cc: | "Ivano Luberti" <luberti(at)archicoop(dot)it>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: begin transaction locks out other connections |
| Date: | 2008-04-11 06:18:24 |
| Message-ID: | 2e78013d0804102318k363c9f39q82eecd5378f8819b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Apr 10, 2008 at 11:29 PM, Dennis Brakhane
<brakhane(at)googlemail(dot)com> wrote:
>
> I believe it does. See
> http://www.postgresql.org/docs/8.3/interactive/sql-set-constraints.html
> and the DEFERRABLE keyword in CREATE TABLE.
>
> Or am I missing something here?
>
Only foreign key contrains checks (and triggers) can be deferred, not the
primary or unique key checks. See the following statement in the same doc
page:
"Currently, only foreign key constraints are affected by this setting. Check
and unique constraints are always effectively not deferrable. Triggers that
are declared as "constraint triggers" are also affected."
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | J Ottery | 2008-04-11 06:53:18 | Postgres on shared network drive |
| Previous Message | Reece Hart | 2008-04-11 05:17:25 | tsearch2 and hyphenated terms |