From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: A couple of TODO notes |
Date: | 2003-10-21 03:42:35 |
Message-ID: | 18086.1066707755@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> * Allow INET subnet tests using non-constants
>> This should say "Allow ... to be indexed" as it's otherwise a nonissue.
> New text is:
> * Allow INET subnet tests to use indexes
> Is that right?
No, because we already index subnet tests against constants. (It's pretty
much like the situation for "column LIKE anchored-pattern" --- we
transform to an indexable range-test.)
>> This is either done or rendered irrelevant, depending on your point of
>> view, by the V3 protocol.
> Do we allow SELECT data to come back as BINARY form (not C strings)
> like we do with BINARY cursors?
Yes, you can make that happen in the V3 protocol: you can select either
text or binary output format for each column. Declaring a cursor BINARY
is in fact irrelevant in V3 protocol.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-10-21 04:04:17 | Re: A couple of TODO notes |
Previous Message | Bruce Momjian | 2003-10-21 03:18:37 | Re: [COMMITTERS] pgsql-server/src backend/main/main.c backend/t ... |