| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joseph Shraibman <jks(at)selectacast(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: error on drop table |
| Date: | 2001-11-30 16:16:34 |
| Message-ID: | 8028.1007136994@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Joseph Shraibman <jks(at)selectacast(dot)net> writes:
> Tom Lane wrote:
>> I don't see an error if I do it that way, but I do see an error if the
>> cursor hasn't yet fetched all the rows:
> What version are you using? I get the error using exactly what I showed you on 7.1.3.
Hmmm ... I was using current sources. I do replicate your result on
7.1.3, however. It looks like 7.1 holds onto a buffer pin for a
completed scan a little longer than 7.2 does. I believe this is related
to my changes of 2001-06-09 14:16, but don't feel like running it to
ground right now. The bottom line is the same in any case: the open
cursor represents a reference to the relation, which should prevent
us from dropping the relation.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-11-30 16:26:05 | Re: Initdb failure with PG 7.1.3 on RH 7.1... |
| Previous Message | Andrew Gould | 2001-11-30 15:46:10 | Re: alter table |