Hi,
I'm looking for a trigger (any language) that can clone the inserted
row and insert it in another postgres server elsewhere. Is this
possible? Practical? Thoughts?
I know there are some replication systems out there, but I'm hoping a
simple trigger will suffice since I only need to clone one
Well, I did, but I clicked the link to Chapter 13 before scrolling down
further to see the Caution section. Heheh.
Thanks for the heads up.
On Sun, 2009-01-11 at 12:12 -0500, Tom Lane wrote:
> Darren Govoni writes:
> > This seems like a bug to me. Is it fixed in the current dev bui
Hi,
I have a simple scenario that is producing incorrect results with
8.3,ubuntu.
I have queries attempting the same "select-for update limit 1". at the
same time. There are 2 rows in my test database.
The first will enter the transaction and only update ONE of the rows it
selected, because it u
tributed scheduling. So nodes competing to
update rows with the same query don't collide and shouldn't have to wait
on another threads updates to get some results.
I'll keep experimenting!
Darren
On Mon, 2008-11-17 at 19:37 -0500, Tom Lane wrote:
> Darren Govoni <[EMAIL PROTECTED
Hi,
I have experimented with PostgreSQL's table locking and FOR UPDATE
capabilities. But what I'm looking for is a row level lock specific to
only a set of rows, not the entire table.
For example, there is a table with many rows. Threads are doing
"SELECTS" to read some rows. They should be allo
