On Tue, Mar 29, 2005 at 03:54:48 +0100,
Olivier Thauvin <[EMAIL PROTECTED]> wrote:
>
> Maybe I will workaround by setting postgres user access as 'trust' for local
> connection only, but I have to reread the doc before :).
Ident is better if you can use domain sockets and the equivalent of
get
>Bug reference: 1576
>Logged by: Sergio Luis SÃÂnchez
>Email address: [EMAIL PROTECTED]
>PostgreSQL version: 7.4.3 and 8.0.1
>Operating system: linux (7.4.3) and WinXP (8.0.1)
>Description:Function UPPER does not give back the
>awaited results
>Details:
>
>Hi.
>
>I'm
>ok.
>i succesfully installed postgresql 8 on my windows xp sp2 machine, few
>weeks ago. i am a newbie to sql generally, as well as to postrges
>i configured my server to run on localhost, everything was fine. i
>need to mention that the machine is part of a active directory
>network, corporate 35
This came up from a user in the IRC channel; while examining his EXPLAIN
ANALYZE output, we found some rather radical discrepancies in the costs
for a merge join, which was resulting in very suboptimal plans. I was
able to reduce his data to a test case as follows:
create table mjtest1 (id integer
Andrew - Supernews <[EMAIL PROTECTED]> writes:
> The cost for the Merge Left Join is clearly preposterous, since the join
> cost can't be lower than the cost of the left branch, as it is an outer
> join and therefore that branch must be run to completion. I do not fully
> understand the cost estima
