From: | "alex b(dot)" <mailinglists1(at)gmx(dot)de> |
---|---|
To: | Postgresql General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: realtime data inserts |
Date: | 2003-05-16 20:27:42 |
Message-ID: | 3EC549BE.5040403@gmx.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers pgsql-performance |
Doug McNaught wrote:
> Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> writes:
>
>
>>On Sat, 2003-05-10 at 21:46, Tom Lane wrote:
>>
>>>Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> writes:
>>>
>>>>On Sat, 2003-05-10 at 11:00, Tom Lane wrote:
>>>>
>>>>>Have you thought about using COPY?
>>>
>>>>Generate a temporary file, and then system("COPY /tmp/foobar ...") ?
>>>
>>>No, copy from stdin. No need for a temp file.
>>
>>But wouldn't that only work if the input stream is acceptable to
>>COPY ?
>
>
> Yes, but you could always pipe it through a script or C program to
> make it so...
lets say I have an about 1kb/s continuus datastream comming in for many
hours and I'd like to store this data in my db using COPY table FROM stdin.
At what time should I COMMIT or close the stream to feed the database
and COPY FROM again?
From | Date | Subject | |
---|---|---|---|
Next Message | Ericson Smith | 2003-05-16 20:33:55 | Re: realtime data inserts |
Previous Message | Luis Rodrigo Gallardo Cruz | 2003-05-16 20:21:22 | Re: [Pgsql-ayuda] Tool for BackUp |
From | Date | Subject | |
---|---|---|---|
Next Message | Ericson Smith | 2003-05-16 20:33:55 | Re: realtime data inserts |
Previous Message | Sean Chittenden | 2003-05-16 20:26:50 | Re: Heads up: 7.3.3 this Wednesday |
From | Date | Subject | |
---|---|---|---|
Next Message | Ericson Smith | 2003-05-16 20:33:55 | Re: realtime data inserts |
Previous Message | Stephan Szabo | 2003-05-15 15:08:52 | Re: [ADMIN] nested query too expensive |