From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | mweilguni(at)sime(dot)com |
Cc: | Hackers List <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Query precompilation? |
Date: | 2001-02-28 03:18:20 |
Message-ID: | 3A9C6DFC.DF44A760@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Mario Weilguni wrote:
>
> (...)
> > >
> > > I don't care about integrity etc!
> >
> > You should !-)
> >
> > You can find some valueable tips in the documentation:
> > http://www.de.postgresql.org/users-lounge/docs/7.0/user/c4929.htm
> >
>
> In the docs there is this paragraph:
> >Disable Auto-commit
> >
> > Turn off auto-commit and just do one commit at the end. Otherwise Postgres
> >is doing a lot of work for each record added. In general when you are doing
> >bulk inserts, you want to turn off some of the database features to gain
> >speed.
>
> This sounds nice, but I've read a lot of postgres documents and still do not
> know how to disable autocommit. Is this possible? And how?
At the moment, use a BEGIN/COMMIT block around a set of insert
statements. Someday we'll likely have an explicit command to affect the
behavior.
- Thomas
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Fischer | 2001-02-28 03:24:52 | Find out when a table was last changed ? |
Previous Message | will trillich | 2001-02-28 02:45:41 | Re: Addison-Wesley looking for authors |
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 2001-02-28 03:21:16 | Re: [ODBC] Re: Release in 2 weeks ... |
Previous Message | Thomas Lockhart | 2001-02-28 03:07:06 | Re: Release in 2 weeks ... |