Re: huge query tree cost too much time to copyObject() - Mailing list pgsql-hackers

From Tom Lane
Subject Re: huge query tree cost too much time to copyObject()
Date
Msg-id 9360.1227581536@sss.pgh.pa.us
Whole thread Raw
In response to huge query tree cost too much time to copyObject()  ("Tao Ma" <feng_eden@163.com>)
List pgsql-hackers
"Tao Ma" <feng_eden@163.com> writes:
> recently, I wrote a really complex SELECT statement which consists of about 
> 20 relations using NATURAL JOIN method and every single relation consists 50 
> columns. It looks like:

Maybe you should rethink your schema design...

> It seems Postgres cost lots of time to copyObject().

You're completely wasting your time to optimize *that*.
        regards, tom lane


pgsql-hackers by date:

Previous
From: ITAGAKI Takahiro
Date:
Subject: Comments to Synchronous replication patch v3
Next
From: Hiroshi Inoue
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Explicitly bind gettext() to the UTF8 locale when in use.