Re: Protect a table against concurrent data changes while allowing to vacuum it - Mailing list pgsql-general

From Bill Moran
Subject Re: Protect a table against concurrent data changes while allowing to vacuum it
Date
Msg-id 20160622165657.47c4f7ee140cf57522cbac2f@potentialtech.com
Whole thread Raw
In response to Re: Protect a table against concurrent data changes while allowing to vacuum it  (Sameer Kumar <sameer.kumar@ashnik.com>)
List pgsql-general
On Wed, 22 Jun 2016 10:20:38 +0000
Sameer Kumar <sameer.kumar@ashnik.com> wrote:

> On Wed, Jun 22, 2016 at 6:08 PM Vlad Arkhipov <arhipov@dc.baikal.ru> wrote:
>
> > I am running PostgreSQL 9.5.
> >
> > CREATE TABLE t (id BIGINT NOT NULL PRIMARY KEY, name TEXT);
> >
> > The constraint that the data must satisfy is `there is no more than 3
> > records with the same name`.
> >
> > I am not in control of queries that modify the table, so advisory locks
> > can hardly be of help to me.
> >
>
> Define a function which does a count of the rows and if count is 3 it
> return false if count is less it returns true.

An exclusion constraint might be a better solution.

--
Bill Moran


pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Postgres 9.5.2 upgrade to 9.6
Next
From: Patrick B
Date:
Subject: Re: Help on recovering my standby