| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: LIMIT NULL |
| Date: | 2009-02-02 19:03:29 |
| Message-ID: | B29CA2FD-2638-4D0C-BD8E-A2604B7B9955@kineticode.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Feb 2, 2009, at 10:17 AM, Tom Lane wrote:
> It's worked the way it does now since 7.1, and no one has complained;
> in fact we've gotten bug reports when it was broken by the int8-limit
> patch. So there are people depending on the behavior.
Yeah, it's very useful. Here's a patch for the docs about it.
Thanks,
David
| Attachment | Content-Type | Size |
|---|---|---|
| limit-null.patch | application/octet-stream | 704 bytes |
| unknown_filename | text/plain | 1 byte |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ries van Twisk | 2009-02-02 19:20:43 | Re: [NOVICE] LATIN2->UTF8 conversation with dblink |
| Previous Message | Tom Lane | 2009-02-02 18:31:54 | Re: [NOVICE] LATIN2->UTF8 conversation with dblink |