Re: [HACKERS] Best practices: MERGE - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: [HACKERS] Best practices: MERGE
Date
Msg-id 200504190337.j3J3bUq28952@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] Best practices: MERGE  (David Fetter <david@fetter.org>)
Responses Re: [HACKERS] Best practices: MERGE
List pgsql-patches
Patch applied.  Thanks.  Sorry for the delay in applying.

---------------------------------------------------------------------------


David Fetter wrote:
> On Tue, Mar 08, 2005 at 12:27:21PM +0800, Christopher Kings-Lynne wrote:
> > >Luckily, PG 8 is available for this.  Do you have a short example?
> >
> > No, and I think it should be in the manual as an example.
> >
> > You will need to enter a loop that uses exception handling to detect
> > unique_violation.
>
> Pursuant to an IRC discussion to which Dennis Bjorklund and
> Christopher Kings-Lynne made most of the contributions, please find
> enclosed an example patch demonstrating an UPSERT-like capability.
>
> Cheers,
> D
> --
> David Fetter david@fetter.org http://fetter.org/
> phone: +1 510 893 6100   mobile: +1 415 235 3778
>
> Remember to vote!

[ Attachment, skipping... ]

>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>       joining column's datatypes do not match

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_autovacuum UPDATE_INTERVAL cmd arg
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: [HACKERS] Best practices: MERGE