From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Alban Hertroys <haramrae(at)gmail(dot)com>, Sherrylyn Branchaw <sbranchaw(at)gmail(dot)com> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Murali M <manips2002(at)gmail(dot)com>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Question about copy from with timestamp format |
Date: | 2015-08-05 05:22:18 |
Message-ID: | 55C19D8A.1020403@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 7/30/15 3:09 PM, Alban Hertroys wrote:
> COPY is a bit special, I'm afraid. For starters, although it works_like_ doing a bunch of INSERTs, it doesn't perform actual INSERTs. Apparently, that also means it won't fire an INSERT rule and thus can't be used with an updatable view. There are no rules on such a view (rules rewrite the query) that would work for COPY.
>
> Now perhaps that sounds like a COPY rule is warranted for cases like these, but that doesn't help, exactly because the COPY command has no place in its syntax for expressions (such as this type conversion). INSERT does, hence we can write a rule for it…
>
> In hindsight it all makes sense. That doesn't bring you any closer to a solution, unfortunately.
By the way, if you're desperate enough to make this work during copy,
you could create a new type that understands that time format. It'd
involve some C coding though.
It would be nice if there was a way to do transforms during COPY. I
vaguely remember some discussion of that on hackers some time ago.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com
From | Date | Subject | |
---|---|---|---|
Next Message | Johann Spies | 2015-08-05 07:38:28 | idle processes |
Previous Message | Jim Nasby | 2015-08-05 05:01:22 | Re: Transaction ID Wraparound Monitoring |