| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Marc Spitzer <marc(at)oscar(dot)eng(dot)cv(dot)net> |
| Cc: | <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: persistent connections, AOLserver (Was: maybe Offtopic : |
| Date: | 2001-12-17 03:40:24 |
| Message-ID: | 20011216193909.T46323-100000@megazone23.bigpanda.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-php pgsql-sql |
On Mon, 17 Dec 2001, Marc Spitzer wrote:
> In article <20011203110458(dot)E93680-100000(at)megazone23(dot)bigpanda(dot)com>,
> Stephan Szabo wrote:
> > On Fri, 30 Nov 2001, Steve Brett wrote:
> >
> >> is there a limit/guide to the number of inserts you should use in a
> >> transaction block ?
> >
> > Not a hard one, but I usually do thousands of rows (around 5k) per
> > transaction when I'm batch inserting, and I usually set it there so
> > I can watch its progress from another db session as the counts rise.
> >
>
> How do you set up the other session to watch?
Usually I just set up something to do throw an occasional query to the
server every so often (small script or something). Something like a
select count(*) or select id order by id desc limit 1 type query.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gary Hoffman | 2001-12-17 06:23:32 | Determing Postgres version |
| Previous Message | Marc Spitzer | 2001-12-17 02:01:06 | Re: persistent connections, AOLserver (Was: maybe Offtopic : |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2001-12-17 03:41:21 | Re: performance tuning in large function / transaction |
| Previous Message | MindTerm | 2001-12-17 02:58:56 | Re: performance tuning in large function / transaction |