-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@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
: Re: [GENERAL] Simple SQL INSERT to avoid duplication failed: why?
On 2013-05-01, Carlo Stonebanks stonec.regis...@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
On 2013-05-01, Carlo Stonebanks stonec.regis...@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
...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Steven Schlansker
Sent: April 30, 2013 7:10 PM
To: Carlo Stonebanks
Cc: 'Tom Lane'; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Simple SQL INSERT to avoid duplication failed: why?
On Apr 30, 2013, at 4:00 PM, Carlo
On Wed, May 1, 2013 at 7:16 AM, Carlo Stonebanks
stonec.regis...@sympatico.ca wrote:
Very good to know, Steve. We're on 9.0 right now but I will investigate as
all the work is for unattended automatic processes which are continuously
streaming data from multiple resources and need to resolve
To: Carlo Stonebanks
Cc: Steven Schlansker; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Simple SQL INSERT to avoid duplication failed: why?
On Wed, May 1, 2013 at 7:16 AM, Carlo Stonebanks
stonec.regis...@sympatico.ca wrote:
Very good to know, Steve. We're on 9.0 right now but I
On May 1, 2013, at 9:36 AM, Carlo Stonebanks stonec.regis...@sympatico.ca
wrote:
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?
Given my
Message-
From: Merlin Moncure [mailto:mmonc...@gmail.com]
Sent: May 1, 2013 11:37 AM
To: Carlo Stonebanks
Cc: Steven Schlansker; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Simple SQL INSERT to avoid duplication failed: why?
On Wed, May 1, 2013 at 7:16 AM, Carlo Stonebanks
stonec.regis
Hi Tom,
There's nothing obviously wrong with that, which means the issue is in
something you didn't show us. Care to assemble a self-contained example?
Unfortunately, it happens erratically and very, very rarely so I can't give
you something that will fail. I expected an occasional failure
On Apr 30, 2013, at 4:00 PM, Carlo Stonebanks stonec.regis...@sympatico.ca
wrote:
Hi Tom,
There's nothing obviously wrong with that, which means the issue is in
something you didn't show us. Care to assemble a self-contained example?
Unfortunately, it happens erratically and very,
Carlo Stonebanks stonec.regis...@sympatico.ca writes:
The only way I can see this happening is that an
acache_mdx_logic_address_validation sneaks in before the insert and after
the NOT EXISTS... SELECT. And for that to occur, the client must be mistaken
and something else MUST be running and
Ok, I tried to be clever and I wrote code to avoid inserting duplicate data.
The calling function has a try-catch to recover from this, but I am curious
as to why it failed:
INSERT INTO
mdx_lib.acache_mdx_logic_address_validation
(
address,
postal_code,
address_id
Carlo Stonebanks stonec.regis...@sympatico.ca writes:
Ok, I tried to be clever and I wrote code to avoid inserting duplicate data.
The calling function has a try-catch to recover from this, but I am curious
as to why it failed:
There's nothing obviously wrong with that, which means the issue
13 matches
Mail list logo
