Re: Simple SQL INSERT to avoid duplication failed: why?
От | Carlo Stonebanks |
---|---|
Тема | Re: Simple SQL INSERT to avoid duplication failed: why? |
Дата | |
Msg-id | 01b101ce4a75$6b2af710$4180e530$@sympatico.ca обсуждение исходный текст |
Ответ на | Re: Simple SQL INSERT to avoid duplication failed: why? (Jasen Betts <jasen@xnet.co.nz>) |
Ответы |
Re: Simple SQL INSERT to avoid duplication failed: why?
|
Список | pgsql-general |
-----Original Message----- From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Jasen Betts Sent: May 4, 2013 7:44 PM To: pgsql-general@postgresql.org Subject: Re: [GENERAL] Simple SQL INSERT to avoid duplication failed: why? On 2013-05-01, Carlo Stonebanks <stonec.register@sympatico.ca> wrote: > There are no client poolers (unless pgtcl has one I don't know about) > so this is unlikely. > > The trigger is an interesting idea to try if it happens again - I > can't keep it for long as it is for a massive cache (used to deflect > calls to a web > service) and will bloat the logs pretty quickly. > > I have to ask myself, is it more likely that I have discovered some PG > anomaly in 9.0 that no one has ever noticed, or that the client has > accidentally launched the process twice and doesn't know it? >> If it's running on a web server and two clients send the same request simultaneously could that cause it to try the >>same task twice simultaneously? It would, but it's not running on a web server. It's a kind of dedicated data warehouse with very limited access. No programshave the right to write to the tables other than the one in question.
В списке pgsql-general по дате отправления: