Thanks for this Peter. I got it working by putting in the changes
suggested by Stephan and adding errno.h
However, I can't get any triggers to work. I'm new to postgresql, and
to triggers, so it's got to be something I'm doing wrong.
The test.sql script only half works. The behaviour is the
On Thursday 04 December 2003 16:36, Stephan Szabo wrote:
> > I thought I was onto a winner with pgplsh, but I can't get it to
> > compile with 7.3.4, although it compiled beautifully with 7.2.1.
>
> It takes a little bit of work to get pgplsh to compile for my devel
> system (notably that I needed
I'll try the fix and compile of pgplsh, as suggested by Stephan. (thanks
:-) I'd assumed that the errors I was seeing were indicative of much
larger compatibility problems. Just shows what "Assume" does :-)
As you say, using trigger worries me, because of rollbacks. I'd thought
of using NOTIFY,
On Thu, 4 Dec 2003, Alan Graham wrote:
> I'm doing a low cost, low performance roll your own replication project,
> between various offices around Australia. The replication is
> asynchronous, and peer to peer. I've looked at the various replication
> projects, and for one reason or another, th
On Thu, 4 Dec 2003, Alan Graham wrote:
> I'm doing a low cost, low performance roll your own replication project,
> between various offices around Australia. The replication is
> asynchronous, and peer to peer. I've looked at the various replication
> projects, and for one reason or another, t
I'm doing a low cost, low performance roll your own replication project,
between various offices around Australia. The replication is
asynchronous, and peer to peer. I've looked at the various replication
projects, and for one reason or another, they're too hard.
My design uses jabber as middlew
