Hi Steven,
Your most recent version pending.c does not crashes
postmaster anymore when PRIMARY KEYS are missing.
Instead it raises notices and errors:
tradein_clients=> BEGIN work; UPDATE iid_listing set city='DELHI testing' where
list_id=23312;
BEGIN
NOTICE: Could not select primary index key
"Rajesh Kumar Mallah." <[EMAIL PROTECTED]> writes:
> # patch -p0 < patch
> patch: malformed patch at line 7: PRIMARY);
I think the patch got mucked up by line-wrapping, either in your mail
program or Steve's ...
regards, tom lane
---(end of
[Rajesh Kumar Mallah]
> Hi can you help me with applying the patch
> i dunno much abt patch
>
> # patch -p0 < patch
> patch: malformed patch at line 7: PRIMARY);
It looks like a context patch. patch --help should tell you how to apply a
context patch. It will also tell you the basic syntax
Hi can you help me with applying the patch
i dunno much abt patch
# patch -p0 < patch
patch: malformed patch at line 7: PRIMARY);
regds
mallah.
On Tuesday 24 September 2002 02:18, Steven Singer wrote:
> On Mon, 23 Sep 2002, Rajesh Kumar Mallah. wrote:
> > Hi
> >
> > Is anyone using
Hi Steven ,
thanks for the reply and letting me know that a primary key is
essential for the replicated tables.
For your information pending.c used to crash postmaster even
when it was not in debug mode. (it was only then i defined
DEBUG_OUTPUT to see whats going on).
Thanks for the patch. But
Hi
Is anyone using dbmirror in production?
I Intend to replicate a set of tables between local and remote servers.
and plan to use dbmirror.
I observe that unless a table has a primary key the trigger recordchange()
which is supposed to be attached to a replicated table does not works properly
