| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Darren Duncan <darren(at)darrenduncan(dot)net> |
| Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PL/Perl Returned Array |
| Date: | 2011-08-13 08:15:20 |
| Message-ID: | 1313223320.9614.0.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On fre, 2011-08-12 at 20:09 -0700, Darren Duncan wrote:
> David E. Wheeler wrote:
> > On Aug 12, 2011, at 6:17 PM, Alex Hunsaker wrote:
> >> Anyway, the attached patch fixes it for me. That is when we don't have
> >> an array state, just return an empty array. (Also adds some
> >> additional comments)
> >
> > Fix confirmed, thank you!
> >
> > +1 to getting this committed before the next beta/RC.
>
> Policy question. If this problem hadn't been detected until after 9.1 was
> declared production, would it have been considered a bug to fix in 9.1.x or
> would it have been delayed to 9.2 since that fix might be considered an
> incompatibility?
Surely this would be a bug fix.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2011-08-13 09:01:57 | Re: Inserting heap tuples in bulk in COPY |
| Previous Message | Bruce Momjian | 2011-08-13 03:37:54 | Re: Transient plans versus the SPI API |