Search Postgresql Archives

Re: Bug? Query plans / EXPLAIN using gigabytes of memory

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 26/04/12 17:16, Toby Corkindale wrote:
On 26/04/12 16:58, Tom Lane wrote:
Toby Corkindale<toby.corkindale@xxxxxxxxxxxxxxxxxxxx> writes:
On 26/04/12 15:30, Tom Lane wrote:
Hm, is the update target an inheritance tree?

The target is the parent table of a bunch of partitions.

How many would "a bunch" be, exactly? I'm fairly sure that the complex
view would get re-planned for each target table ...

The table being updated (line) has 57 child tables.

Although we are specifying a value for the column which they are partitioned on.

ie.

CREATE TABLE line (file_id, lineno, status,
                   primary key (file_id, lineno));
CREATE TABLE line_1 ( CHECK (file_id=1) ) INHERITS (line);
CREATE TABLE line_2 ( CHECK (file_id=2) ) INHERITS (line);

UPDATE line SET status = something
FROM complex_view cv
WHERE cv.file_id = 2 AND line.file_id=2;

--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux