Hi,
I'm developping a geographical object type, very close to the geographic
type of PG. For the moment it is set up as external functions...
I would like to add indexing capabilities, and I have seen that indexing for
PG geographical objects is on the TODO list for 7.1.
I would like to get in
On Thu, 14 Sep 2000, The Hermit Hacker wrote:
>
> Okay, logically I think this makes sense, but its not working ... should
> it?
>
> globalmatch=# insert into auth_info_new
> globalmatch-# select ai.* from auth_info ai, auth_info_new ain
> globalmatch-# where ai.username != ain.username;
> INSE
> It seems that the parser now emits some kind of function call for LIKE
> expressions, whereas the optimizer's code to use indexes for LIKE is
> looking for an operator.
> I have more pressing things to do than try to teach the optimizer about
> looking for function calls as well as operators, so
Okay, logically I think this makes sense, but its not working ... should
it?
globalmatch=# insert into auth_info_new
globalmatch-# select ai.* from auth_info ai, auth_info_new ain
globalmatch-# where ai.username != ain.username;
INSERT 0 0
auth_info has 14k tuples, but some are duplicates ... I
At 22:43 13/09/00 -0400, Tom Lane wrote:
>
>> Am I correct that someone was working on allowing a column order to be
>> specified in COPY commands? If so, this would fix the problem, I think.
>
>No, that is a kluge that would allow pg_dump to work around ALTER
>TABLE's fundamental inadequacy. It'
Philip Warner <[EMAIL PROTECTED]> writes:
> At 12:34 13/09/00 -0400, Tom Lane wrote:
>> The command needs to read "basetype = any".
> The particular piece of code (findTypeByOid) that does this is used to
> display types other places (eg. function return types). My guess is that I
> should use th
At 12:34 13/09/00 -0400, Tom Lane wrote:
>
>The command needs to read "basetype = any". I guess you'll have to
Does this apply to any other parts of 'CREATE AGGREGATE' (or anywhere else?)
Philip Warner| __
At 12:34 13/09/00 -0400, Tom Lane wrote:
>
>The command needs to read "basetype = any". I guess you'll have to
>special-case this in pg_dump (or more accurately, change the special
>case that's probably there now for aggbasetype = 0). I think I changed
>the aggregate regression test to exercise
At 10:48 13/09/00 -0700, Mikheev, Vadim wrote:
>> My vote is for a random number, and then someone can write
>> the tools to display the file info. I'll even volunteer to
>> work on them...
>
>Ok. If someone will decide to implement this please try to use
>RelFileNode structure defined in storage
Andreas Degert <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> writes:
>> Also, it might help to look at the output of EXPLAIN VERBOSE for
>> the misbehaving query. That would let us see what indexscan limits
>> are being generated.
> This is the output of
> explain verbose select cou
10 matches
Mail list logo
