| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Vincent de Phily <vincent(dot)dephily(at)mobile-devices(dot)fr> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Receiving many more rows than expected |
| Date: | 2014-05-09 11:01:32 |
| Message-ID: | 18293.1399633292@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Vincent de Phily <vincent(dot)dephily(at)mobile-devices(dot)fr> writes:
> In case it changes anything, this is the uncut (but still anonimized)
> function:
> query = """UPDATE foo SET processing = 't' WHERE id IN
> (SELECT id FROM foo WHERE processing = 'f' ORDER BY id ASC LIMIT %d
> FOR UPDATE)
> RETURNING *""" % (conf_getint('DEFAULT', 'push_count', 5000),)
Well, of course this view of things exposes a relevant failure mode
you hadn't mentioned: maybe sometimes the conf_getint() call returns
something other than 5000?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vincent de Phily | 2014-05-09 12:36:36 | Re: Receiving many more rows than expected |
| Previous Message | Vincent de Phily | 2014-05-09 08:45:43 | Re: Receiving many more rows than expected |