Re: [PATCHES] Best practices: MERGE - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: [PATCHES] Best practices: MERGE
Date
Msg-id 42647EA8.2080307@familyhealth.com.au
Whole thread Raw
In response to Re: Best practices: MERGE  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [PATCHES] Best practices: MERGE  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Is that broken?

http://momjian.postgresql.org/main/writings/pgsql/sgml/build.html

Chris

Bruce Momjian wrote:
> 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
>
>

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Best practices: MERGE
Next
From: Sailesh Krishnamurthy
Date:
Subject: Re: Call to build-in operator from new operator