From: | Alfred Perlstein <bright(at)wintelcom(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, prlw1(at)cam(dot)ac(dot)uk, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: pg_dump possible fix, need testers. (was: Re: [HACKERS] pg_dump disaster) |
Date: | 2000-01-23 07:05:11 |
Message-ID: | 20000122230510.I26520@fw.wintelcom.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> [000122 22:17] wrote:
> Alfred Perlstein <bright(at)wintelcom(dot)net> writes:
> > I really hope the originator of the problem report will get back to
> > us to make sure it's settled.
>
> > *poking Patrick Welche*
>
> Um, I didn't have any trouble at all reproducing Patrick's complaint.
> pg_dump any moderately large table (I used tenk1 from the regress
> database) and try to load the script with psql. Kaboom.
Can you try it on sources from before my initial patches were
applied, and from before the initial non-blocking connections
patches from Ewan Mellor were applied?
>From my point of view none of my code should be affecting those that
don't explicitly use PQsetnonblocking(), which is nothing besides
the application i'm developing in-house.
I'm currently investigating that possibility.
thanks,
-Alfred
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2000-01-23 08:16:35 | Re: [HACKERS] char_length()? |
Previous Message | Alfred Perlstein | 2000-01-23 06:02:56 | Re: pg_dump possible fix, need testers. (was: Re: [HACKERS] pg_dump disaster) |