Re: Is this a reasonable use for advisory locks? - Mailing list pgsql-general

From Michael Lewis
Subject Re: Is this a reasonable use for advisory locks?
Date
Msg-id CAHOFxGpXj7j5dYSudWz5f5cRaGSOY2sM=P9y-oSLNxUB-VJ+vA@mail.gmail.com
Whole thread Raw
In response to Re: Is this a reasonable use for advisory locks?  (Perryn Fowler <perryn@fresho.com>)
List pgsql-general
How many of these processes do you expect to have running concurrently? How long does that API call take? Might it be better to update the customer (or in a separate table as suggested) as "catch up charge process started at" and then clear that or set completed time in another column to serialize? That way, no need to hold that db connection while doing external work via api.

pgsql-general by date:

Previous
From: Philip Semanchuk
Date:
Subject: Could Postgres warn about incorrect volatility class?
Next
From: JORGE MALDONADO
Date:
Subject: Re: Backing up a DB excluding certain tables