My apologies for making confusion with new thread. Yes its same issue related to earlier post. I was trying to figure out how to ensure unique values for columns (billing_account_guid, ban). If i add partition key to constraint , it wont be possible what im looking for. My use case as below INSERT INTO t1 SELECT * from t2 ON CONFLICT (billing_account_guid,ban) DO UPDATE SET something…
Or INSERT INTO t1 SELECT * from t2 ON CONFLICT constraint (pk or uk)(billing_account_guid,ban) DO UPDATE SET something… Thanks Sent from Yahoo Mail for iPhone On Thursday, July 8, 2021, 7:12 PM, Mike Sofen <mso...@runbox.com> wrote: I believe this thread qualifies for the funniest thread of 2021 (so far). And yes, this is a top post. :-) Mike Sofen -----Original Message----- From: Alvaro Herrera <alvhe...@alvh.no-ip.org> Sent: Thursday, July 08, 2021 3:29 PM To: Justin Pryzby <pry...@telsasoft.com> Cc: Nagaraj Raj <nagaraj...@yahoo.com>; pgsql-performa...@postgresql.org Subject: Re: Partition column should be part of PK On 2021-Jul-08, Justin Pryzby wrote: > If I'm not wrong, this is the same thing you asked 2 week ago. > > If so, why not continue the conversation on the same thread, and why > not reference the old thread ? > > I went to the effort to find the old conversation. > https://www.postgresql.org/message-id/20210625042228.GJ29179@telsasoft > .com Actually, it looks like you're replying to the same email you replied to two weeks ago. -- Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/
