Re: Partitioning option for COPY

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: Emmanuel Cecchet <manu(at)asterdata(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Partitioning option for COPY
Date: 2009-11-12 01:18:49
Message-ID: 4AFB6279.1070207@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> We can use an INSERT trigger to route tuples into partitions even now.
> Why do you need an additional router for COPY? Also, it would be nicer
> that the router can works not only in COPY but also in INSERT.

Yeah, but performance on an insert trigger is impractical for large
volumes of data.

--Josh Berkus

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Gierth 2009-11-12 01:27:57 NULL-handling in aggregate(DISTINCT ...)
Previous Message Itagaki Takahiro 2009-11-12 01:13:03 Re: Partitioning option for COPY