On 06/19/2018 03:13 PM, Asif Ali wrote:
> please just tell me the site i will do it right away and i have marked
> it junked so many times , i will keep spamming it until my email address
> is removed from the list
https://lists.postgresql.org/unsubscribe/
>
> Bye
>
> ------------------------------------------------------------------------
> *From:* James Keener <jim@jimkeener.com>
> *Sent:* Wednesday, June 20, 2018 3:11 AM
> *To:* pgsql-general@lists.postgresql.org; Asif Ali; Alban Hertroys; Ravi
> Krishna
> *Cc:* PG mailing List
> *Subject:* Re: Load data from a csv file without using COPY
> Seriously, stop spamming the list and stop cursing and acting like a
> petulant child. Go to the site and unsubscribe or use a mail client that
> understands the standard list headers.
>
> On June 19, 2018 6:06:59 PM EDT, Asif Ali <asif2k@hotmail.com> wrote:
>
> how the fuck i unsubscribe to this mailing list , i get more than
> 100 emails a day
>
> Bye
>
> ------------------------------------------------------------------------
> *From:* Alban Hertroys <haramrae@gmail.com>
> *Sent:* Wednesday, June 20, 2018 2:10 AM
> *To:* Ravi Krishna
> *Cc:* PG mailing List
> *Subject:* Re: Load data from a csv file without using COPY
>
> > On 19 Jun 2018, at 22:16, Ravi Krishna <srkrishna@yahoo.com> wrote:
> >
> > In order to test a real life scenario (and use it for benchmarking) I want to load large number of data from
csvfiles.
> > The requirement is that the load should happen like an application writing to the database ( that is, no COPY
command).
> > Is there a tool which can do the job. Basically parse the csv file and insert it to the database row by row.
> >
> > thanks
>
> I think an easy approach would be to COPY the CSV files into a
> separate database using psql's \copy command and then pg_dump that
> as separate insert statements with pg_dump —inserts.
>
> Alban Hertroys
> --
> If you can't see the forest for the trees,
> cut the trees and you'll find there is no forest.
>
>
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
Adrian Klaver
adrian.klaver@aklaver.com
