Re: Partitioning... -> solved - Mailing list pgsql-general

From Milen Kulev
Subject Re: Partitioning... -> solved
Date
Msg-id 014601c68fea$fa0c57f0$0a00a8c0@trivadis.com
Whole thread Raw
In response to Re: Partitioning...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Thanks Tom,
OFFSET is even better solution for me .

Regards. Milen

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Wednesday, June 14, 2006 3:57 PM
To: Milen Kulev
Cc: 'Jim C. Nasby'; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Partitioning...


"Milen Kulev" <makulev@gmx.net> writes:
> Thanks Jim, the "trick" worked for me !

>> You might need to add an ORDER BY to the subquery to ensure
>> PostgreSQL doesn't pull it into the main query.

Actually, the usual trick is "OFFSET 0", which works just as well as an optimization fence and doesn't force any
significant extra work. Of course, if you *need* an ORDER BY then that's what to use, but it's overkill if you just
want
to prevent flattening the subquery.

            regards, tom lane


pgsql-general by date:

Previous
From: "Relyea, Mike"
Date:
Subject: Out of memory error in 8.1.0 Win32
Next
From: Terry Lee Tucker
Date:
Subject: Performance Question