From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] libpq and SPI |
Date: | 1999-03-14 18:10:32 |
Message-ID: | 199903141810.NAA00388@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Reversed out. Attached is the patch.
> Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Applied.
> >
> >> Just in case you'd like to see what I was talking about, I am attaching
> >> my patch to src/interfaces/libpq/fe-exec.c to prevent utility functions
> >> called from SPI from locking up the client.
>
> Uh, I didn't actually believe that that patch was a good idea. Hacking
> libpq to survive a protocol violation committed by the backend is *not*
> a solution; the correct answer is to fix the backend. Otherwise we will
> have to discover similar workarounds for other clients that do not
> use libpq (ODBC, for example).
>
> Please reverse out that patch until someone can find some time to look
> at the issue. (I will, if no one else does, but it would probably be
> more efficient for someone who already knows something about SPI to
> fix it...)
>
> regards, tom lane
>
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
Attachment | Content-Type | Size |
---|---|---|
unknown_filename | text/plain | 3.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-03-14 18:20:59 | Re: [HACKERS] libpq and SPI |
Previous Message | Tom Lane | 1999-03-14 17:51:57 | Re: [HACKERS] Problems with >2GB tables on Linux 2.0 |