On Mon, 2009-10-26 at 17:23 +, Dean Rasheed wrote:
If it's of any relevance, I'm currently using an optimised build, with
assert checking off.
[Linux x86_64, 2 core Intel Core2]
Ok, I'm able to reproduce it now. Thanks for looking into it!
Regards,
Jeff Davis
--
Sent via
2009/10/25 Simon Riggs si...@2ndquadrant.com:
On Mon, 2009-10-19 at 17:48 +0100, Dean Rasheed wrote:
This is a WIP patch to replace the after-trigger queues with TID bitmaps
to prevent them from using excessive amounts of memory. Each round of
trigger executions is a modified bitmap heap
2009/10/25 Jeff Davis pg...@j-davis.com:
On Mon, 2009-10-19 at 17:48 +0100, Dean Rasheed wrote:
This is a WIP patch to replace the after-trigger queues with TID bitmaps
to prevent them from using excessive amounts of memory. Each round of
trigger executions is a modified bitmap heap scan.
On Mon, 2009-10-26 at 13:28 +, Dean Rasheed wrote:
It works for all kinds of trigger events,
and is intended as a complete drop-in replacement for the after
triggers queue.
All of those seem false in the general case. What will you do?
At this point I'm looking for more feedback as
On Mon, 2009-10-26 at 13:41 +, Dean Rasheed wrote:
I did a quick bit of testing, and I think that there is a
locking/concurrency problem :-(
Unfortunately I can't reproduce the problem on my machine; it always
passes.
If you have a minute, can you try to determine if the problem can happen
2009/10/26 Simon Riggs si...@2ndquadrant.com:
On Mon, 2009-10-26 at 13:28 +, Dean Rasheed wrote:
It works for all kinds of trigger events,
and is intended as a complete drop-in replacement for the after
triggers queue.
All of those seem false in the general case. What will you do?
At
2009/10/26 Jeff Davis pg...@j-davis.com:
On Mon, 2009-10-26 at 13:41 +, Dean Rasheed wrote:
I did a quick bit of testing, and I think that there is a
locking/concurrency problem :-(
Unfortunately I can't reproduce the problem on my machine; it always
passes.
That's odd. It happens
On Mon, Oct 26, 2009 at 9:46 AM, Simon Riggs si...@2ndquadrant.com wrote:
On Mon, 2009-10-26 at 13:28 +, Dean Rasheed wrote:
It works for all kinds of trigger events,
and is intended as a complete drop-in replacement for the after
triggers queue.
All of those seem false in the general
On Mon, 2009-10-19 at 17:48 +0100, Dean Rasheed wrote:
This is a WIP patch to replace the after-trigger queues with TID bitmaps
to prevent them from using excessive amounts of memory. Each round of
trigger executions is a modified bitmap heap scan.
This is an interesting patch. The
On Mon, 2009-10-19 at 17:48 +0100, Dean Rasheed wrote:
This is a WIP patch to replace the after-trigger queues with TID bitmaps
to prevent them from using excessive amounts of memory. Each round of
trigger executions is a modified bitmap heap scan.
Can you please take a look at my patch here:
On Mon, Oct 19, 2009 at 12:48 PM, Dean Rasheed
dean.a.rash...@googlemail.com wrote:
This is a WIP patch to replace the after-trigger queues with TID bitmaps
to prevent them from using excessive amounts of memory. Each round of
trigger executions is a modified bitmap heap scan.
If the bitmap
2009/10/19 Robert Haas robertmh...@gmail.com:
On Mon, Oct 19, 2009 at 12:48 PM, Dean Rasheed
dean.a.rash...@googlemail.com wrote:
This is a WIP patch to replace the after-trigger queues with TID bitmaps
to prevent them from using excessive amounts of memory. Each round of
trigger executions
12 matches
Mail list logo
