Christopher Browne <[EMAIL PROTECTED]> writes:
> The DOMAIN case I mentioned the other day had something odd going on
> that LOST the type information associated with the domain. Albeit
> that was on 7.3, whereas the changes in DOMAIN functionality that make
> them meaningfully useful come in 7.4.
Stephan Szabo <[EMAIL PROTECTED]> writes:
> On Fri, 1 Aug 2003, Christopher Browne wrote:
>> Stephan Szabo said:
>> > What version are you using? In 7.3 and up it should be willing to
>> > consider moving the clause down, unless there's something like a type
>> > mismatch (because in that case it
On Fri, 1 Aug 2003, Christopher Browne wrote:
> Stephan Szabo said:
> >
> >
> > What version are you using? In 7.3 and up it should be willing to
> > consider moving the clause down, unless there's something like a type
> > mismatch (because in that case it may not be equivalent without a bunch
>
Stephan Szabo said:
>
> On Thu, 31 Jul 2003, Christopher Browne wrote:
>
>> select * from log_table where request_time between 'june 11 2003'
>> and
>>'june 12 2003';
>>
>> returns a plan:
>> Subquery Scan log_table (cost=0.00..10950.26 rows=1
Stephan Szabo wrote:
On Thu, 31 Jul 2003, Christopher Browne wrote:
select * from log_table where request_time between 'june 11 2003' and
'june 12 2003';
returns a plan:
Subquery Scan log_table (cost=0.00..10950.26 rows=177126 width=314)
->
On Thu, 31 Jul 2003, Christopher Browne wrote:
> select * from log_table where request_time between 'june 11 2003' and
>'june 12 2003';
>
> returns a plan:
> Subquery Scan log_table (cost=0.00..10950.26 rows=177126 width=314)
> -> Append