Re: huge query tree cost too much time to copyObject()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Tao Ma" <feng_eden(at)163(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: huge query tree cost too much time to copyObject()
Date: 2008-11-25 02:52:16
Message-ID: 9360.1227581536@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Tao Ma" <feng_eden(at)163(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 2008-11-25 03:00:37 Re: Re: [COMMITTERS] pgsql: Explicitly bind gettext() to the UTF8 locale when in use.
Previous Message ITAGAKI Takahiro 2008-11-25 02:42:00 Comments to Synchronous replication patch v3