| From: | Oliver Crosby <ryusei(at)gmail(dot)com> |
|---|---|
| To: | Sven Willenberger <sven(at)dmv(dot)com> |
| Cc: | Dawid Kuroczko <qnex42(at)gmail(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, jd(at)commandprompt(dot)com, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Looking for tips |
| Date: | 2005-07-19 21:04:04 |
| Message-ID: | 1efd553a050719140462d41468@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> since triggers work with COPY, you could probably write a trigger that
> looks for this condition and does the ID processsing you need; you could
> thereby enjoy the enormous speed gain resulting from COPY and maintain
> your data continuity.
So... (bear with me here.. trying to make sense of this)..
With triggers there's a way I can do the parsing I need to on a log
file and react to completed events in non-sequential order (you can
ignore that part.. it's just how we piece together different related
events) and then have perl/DBD::Pg invoke a copy command (which, from
what I can tell, has to operate on a file...) and the copy command can
feed the ID I need back to perl so I can work with it...
If that doesn't hurt my brain, then I'm at least kinda confused...
Anyway. Heading home now. I'll think about this more tonight/tomorrow.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alon Goldshuv | 2005-07-19 21:05:56 | Re: COPY FROM performance improvements |
| Previous Message | Sven Willenberger | 2005-07-19 20:46:01 | Re: Looking for tips |