On Wed, Oct 7, 2009 at 3:09 AM, Alvaro Herrera
wrote:
> Stuart Bishop wrote:
>
>> >I don't think the committed patch touches anything involved in what
>> >you're testing, but if you could grab CVS tip from the 8.4 branch (or
>> >the snapshot from ftp.postgresql.org:/pub/snapshot/stable/8.4 ) and g
Stuart Bishop wrote:
> >I don't think the committed patch touches anything involved in what
> >you're testing, but if you could grab CVS tip from the 8.4 branch (or
> >the snapshot from ftp.postgresql.org:/pub/snapshot/stable/8.4 ) and give
> >it a try, that'd be great.
>
> I trigger the same err
Alvaro Herrera wrote:
> I think the previous patch to snapmgr.c was mistaken. Instead of fixing
> a single trouble spot, we're better off fixing PushActiveSnapshot so
> that any use of it that involves a snapshot that's subject to a future
> command counter update should create a new copy.
For a
Alvaro Herrera wrote:
> create trigger onetest_t before update on onetest for each row
> execute procedure upd();
>
> insert into onetest select a, repeat('xyzxz', 100), 'new' from
> generate_series(1, 50) a;
>
> BEGIN;
> SET transaction isolation level SERIALIZABLE;
> UPDATE onetest SE
I think the previous patch to snapmgr.c was mistaken. Instead of fixing
a single trouble spot, we're better off fixing PushActiveSnapshot so
that any use of it that involves a snapshot that's subject to a future
command counter update should create a new copy.
This is correct because the 8.3 code
Alvaro Herrera wrote:
> Here's a slightly smaller test case; basically I removed the tsearch2
> cruft and extra columns in the table. One thing of note is that if the
> COPY commands is reduced to occupy less than one page in the target
> table, the problem does not occur.
And here's an even sma
Alvaro Herrera wrote:
> Stuart Bishop wrote:
> > The test case (invisible.sh) and required dump (foodump.sql - 60k) are
> > at http://www.stuartbishop.net/invisible/
>
> Got it, thanks, looking.
Here's a slightly smaller test case; basically I removed the tsearch2
cruft and extra columns in the
Stuart Bishop wrote:
> On Tue, Oct 6, 2009 at 8:28 PM, Alvaro Herrera
> wrote:
> > mmkay. So, any luck in constructing a test case?
>
> Yes. Just no luck getting it sent to the mailing list - seems to
> silently drop emails with attachments on me :-P
:-(
> The test case (invisible.sh) and req
On Tue, Oct 6, 2009 at 8:28 PM, Alvaro Herrera
wrote:
> Stuart Bishop wrote:
>>
>>
>> On Mon, Oct 5, 2009 at 11:00 PM, Alvaro Herrera
>> wrote:
>> >Stuart Bishop wrote:
>> >>On Mon, Oct 5, 2009 at 4:22 PM, Alban Hertroys
>> >> wrote:
>> >
>> >>> A similar issue was discussed just recently here:
Stuart Bishop wrote:
>
>
> On Mon, Oct 5, 2009 at 11:00 PM, Alvaro Herrera
> wrote:
> >Stuart Bishop wrote:
> >>On Mon, Oct 5, 2009 at 4:22 PM, Alban Hertroys
> >> wrote:
> >
> >>> A similar issue was discussed just recently here:
> >>> http://archives.postgresql.org/pgsql-general/2009-09/msg01
On Mon, Oct 5, 2009 at 11:00 PM, Alvaro Herrera
wrote:
Stuart Bishop wrote:
On Mon, Oct 5, 2009 at 4:22 PM, Alban Hertroys
wrote:
> A similar issue was discussed just recently here:
> http://archives.postgresql.org/pgsql-general/2009-09/msg01219.php
>
> That issue involved cursors though
Stuart Bishop wrote:
> On Mon, Oct 5, 2009 at 4:22 PM, Alban Hertroys
> wrote:
> > A similar issue was discussed just recently here:
> > http://archives.postgresql.org/pgsql-general/2009-09/msg01219.php
> >
> > That issue involved cursors though (and a serializable isolation level, but
> > you ha
On Mon, Oct 5, 2009 at 4:22 PM, Alban Hertroys
wrote:
> On 5 Oct 2009, at 8:58, Stuart Bishop wrote:
>
>> I'm running our products test suite against PostgreSQL 8.4.1. The test
>> suite runs fine against 8.3.7.
>>
>> With 8.4.1, some of our tests are failing with the exception
>> 'attempted to loc
On 5 Oct 2009, at 8:58, Stuart Bishop wrote:
I'm running our products test suite against PostgreSQL 8.4.1. The test
suite runs fine against 8.3.7.
With 8.4.1, some of our tests are failing with the exception
'attempted to lock invisible tuple'. The failures are repeatable -
they crash every tim
I'm running our products test suite against PostgreSQL 8.4.1. The test
suite runs fine against 8.3.7.
With 8.4.1, some of our tests are failing with the exception
'attempted to lock invisible tuple'. The failures are repeatable -
they crash every time at the same point. They crash no matter if the
15 matches
Mail list logo
