Re: Partition Help
Rick,
I am glad I could help, but I am not quite sure you understand the purpose/use of the trigger to would be
INSERT INTO child_1000 VALUES (NEW.*);
To insert by column name, then it would be:
INSERT INTO child_1000
INSERT INTO child_1000
( col_a, col_b, col_c)
VALUES
(NEW.col_a, NEW.col_b, NEW.col_c);
On Wed, Apr 29, 2015 at 7:25 PM, akshunj <rickjackson001@gmail.com> wrote:
Melvin, thanks. Syntax was indeed the problem there. Any idea how to pass the
original query to the child table? My insert has 113 parameters passed in,
but based on the constraint violations I am seeing, it seems they are not
making. I suspect that: VALUE (NEW.*) does not pass in the original query,
only the column I used for the comparison?
--
View this message in context: http://postgresql.nabble.com/Re-Partition-Help-tp5847286p5847360.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
--
Melvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
В списке pgsql-general по дате отправления:
Предыдущее
От: Qingqing ZhouДата:
Сообщение: how to read all physical rows (visible or not) from a heap