Re: Bug: Missing tuples in results written to file

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Erwin Brandstetter" <brandstetter(at)falter(dot)at>
Cc: <pgadmin-support(at)postgresql(dot)org>
Subject: Re: Bug: Missing tuples in results written to file
Date: 2006-10-17 15:41:35
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E40176D6B1@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

> -----Original Message-----
> From: Erwin Brandstetter [mailto:brandstetter(at)falter(dot)at]
> Sent: 17 October 2006 16:06
> To: Dave Page
> Cc: pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] Bug: Missing tuples in results
> written to file
>
>
> It does not happen every time. In my case, it happens in like
> 10-50% of
> the time.

I've run at least 20-30 tests now.

> My best guess is a timing issue. Maybe my sepcial setup adds
> to it again
> (SSH connection with port forwarding to remote server).
> However, I have run tests with almost saturated network
> connection and
> it didn't make a noteable difference.

If it were timing then it would affect the grid as well as it's the same
loop around the query thread used for both options before displaying or
saving the data.

> Tried it with a number of different sources. tables, views
> (simple and
> complex). It randomly happens with each of them.
> When I chose a _new_ output file, then it happens almost every time;
> when I change the query or any setting, it happens often;
> when repeating
> the same export it happens rarely (but still randomely).

With a new file, will it fail on a system table such as pg_class, or
just your data?

Regards, Dave.

In response to

Browse pgadmin-support by date

  From Date Subject
Next Message Nick Farina 2006-10-17 22:33:41 OS-X Tidbits
Previous Message Dave Page 2006-10-17 15:19:24 Re: Query tool database selection (was: Beta 3 crashing reproducably)