[Catching up on old threads.]
On Sat, Nov 17, 2012 at 03:40:49PM +0100, Hannu Krosing wrote:
> On 11/17/2012 03:00 PM, Markus Wanner wrote:
>> On 11/17/2012 02:30 PM, Hannu Krosing wrote:
>>> Is it possible to replicate UPDATEs and DELETEs without a primary key in
>> No. There must be some way to logically identify the tuple.
> It can be done as selecting on _all_ attributes and updating/deleting
> just the first matching row
> create cursor ...
> select from t ... where t.* = (....)
> fetch one ...
> delete where current of ...
> This is on distant (round 3 or 4) roadmap for this work, just was
> if you had found any better way of doing this :)
That only works if every attribute's type has a notion of equality ("xml" does
not). The equality operator may have a name other than "=", and an operator
named "=" may exist with semantics other than equality ("box" is affected).
Code attempting this replication strategy should select an equality operator
the way typcache.c does so.
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2013-01-13 00:47:18|
|Subject: Re: Re: [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4)|
|Previous:||From: Bruce Momjian||Date: 2013-01-13 00:09:31|
|Subject: Latex longtable format|