Hi David,
On Mon, Jul 10, 2017 at 10:02 PM, David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Mon, Jul 10, 2017 at 7:32 AM, Alexander Farber <
> alexander.far...@gmail.com> wrote:
>
>>
>> However there is a problem: I can not use a "single-instance" cronjob to
>> run words_expire_games
On Mon, Jul 10, 2017 at 7:32 AM, Alexander Farber <
alexander.far...@gmail.com> wrote:
>
> However there is a problem: I can not use a "single-instance" cronjob to
> run words_expire_games hourly.
>
​Setup a cron job that invokes the servlet - probably via "curl"
My question is if I should ensur
"FOR UPDATE" is part of "SELECT" not part of "UPDATE".
You can select the rows "for update" which will lock those rows. You
can then loop over the the results of the 'select' to do the rest of
your logic.
Be careful doing this if other things are also updating these rows.
With SKIP LOCKED you ca
I have tried:
FOR _gid, _loser, _winner IN
UPDATE words_games
SET finished = CURRENT_TIMESTAMP
WHERE finished IS NULL
AND played1 IS NOT NULL
AND played2 IS NOT NULL
AND (played1 < CURRENT_TIMESTAMP - INTERVAL '24 hours'
Good afternoon,
in PostgreSQL 9.5 with pgbouncer (having "pool_mode = session" and
"server_reset_query = DISCARD ALL") 2-player games are stored in the
following table:
CREATE TABLE words_games (
gid SERIAL PRIMARY KEY,
created timestamptz NOT NULL,
finished timestamptz,
