From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Joerg Hessdoerfer <Joerg(dot)Hessdoerfer(at)sea-gmbh(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Continuous inserts... |
Date: | 2000-08-18 15:18:07 |
Message-ID: | Pine.BSF.4.10.10008180814340.1321-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Fri, 18 Aug 2000, Joerg Hessdoerfer wrote:
> Good idea - I immediately tested it - rules rule! That seems to work perfectly,
> and the client doesn't even see it happen (except for 'selects', one would
> have to setup
> a rule to return something meaningful then...).
>
> I did:
> Two tables, a and b.
> Normally, insert into a.
> When Vacuuming starts, create rule on a to insert into b
> Vacuum a
> drop rule
> copy records from b to a
> vacuum b
>
> Why did you suppose three tables? Did I overlook something?
I didn't try with vacuum, I just did a table lock and that
seemed to still hang the inserts with two tables, so I figured
maximum safety was adding the third table. If it works with two
that's much cooler. Was this with real data or just a small test
set?
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2000-08-18 15:21:45 | Re: update rule loops |
Previous Message | Poul L. Christiansen | 2000-08-18 15:01:36 | update rule loops |