I'm seeing a problem with the query planner not doing what's expected, and I
think it is because we are using composite fields. Here is a stripped down
example.
create type type1 as ( part1 varchar, part2 varchar);
create table table1 (field1 type1, field2 varchar);
create function get_part1(ty
Steve Rogerson writes:
> I'm seeing a problem with the query planner not doing what's expected, and I
> think it is because we are using composite fields. Here is a stripped down
> example.
> create type type1 as ( part1 varchar, part2 varchar);
> create table table1 (field1 type1, field2 varch
Hello !
There is one's more question, which way I have to determine that void *
randBuf acceptable or not for bytea type ?
Thanks in advance.
On Fri, May 3, 2013 at 9:44 PM, Yuriy Rusinov wrote:
> Thanks a lot, I have corrected and bug was fixed.
>
>
> On Fri, May 3, 2013 at 6:42 PM, Tom Lane
Say I have a select like this.
SELECT * FROM table where field = X OR field = Y limit 1
And I have two records one that matches X and one that matches Y will I
always get X because the evaluation will stop after the first clause in the
OR matches?
What about for IN (X, Y)
how about if I am doin
