Just to dig up an old thread from last month:
In case anyone was wondering we finally got a free day to put in the new
version of the software, and it's greatly improved the performance. The
solutions we employed were as follows:
- recompile everything with ecpg -t for auto-commit
- vacuum run b
Hi all,
> No wonder, considering that your "less than 10 rows" table contains
> something upwards of 10 tuples:
>
> > INFO: --Relation public.plc_fldio--
> > INFO: Pages 1221: Changed 3, reaped 256, Empty 0, New 0; Tup 108137: Vac
> > 4176, Keep/VTL 108133/108133, UnUsed 19, MinLen 84, MaxL
On Thu, Jul 14, 2005 at 08:28:24PM -0400, Alvaro Herrera wrote:
> On Fri, Jul 15, 2005 at 09:42:12AM +1000, Alison Winters wrote:
>
> > INFO: Pages 1221: Changed 3, reaped 256, Empty 0, New 0; Tup 108137: Vac
> > 4176, Keep/VTL 108133/108133, UnUsed 19, MinLen 84, MaxLen 84; Re-using:
> > Free
On Fri, Jul 15, 2005 at 09:42:12AM +1000, Alison Winters wrote:
> > > Our application requires a number of processes to select and update rows
> > > from a very small (<10 rows) Postgres table on a regular and frequent
> > > basis. These processes often run for weeks at a time, but over the
> > >
Alison Winters wrote:
> Hi,
>
>
>>>Our application requires a number of processes to select and update rows
>>>from a very small (<10 rows) Postgres table on a regular and frequent
>>>basis. These processes often run for weeks at a time, but over the
>>>space of a few days we find that updates sta
[EMAIL PROTECTED] (Alison Winters) writes:
>>> Our application requires a number of processes to select and update rows
>>> from a very small (<10 rows) Postgres table on a regular and frequent
>>> basis. These processes often run for weeks at a time, but over the
>>> space of a few days we find t
Hi,
> > Our application requires a number of processes to select and update rows
> > from a very small (<10 rows) Postgres table on a regular and frequent
> > basis. These processes often run for weeks at a time, but over the
> > space of a few days we find that updates start getting painfully sl
On Thu, 2005-07-14 at 15:08 +1000, Alison Winters wrote:
> Hi,
>
> Our application requires a number of processes to select and update rows
> from a very small (<10 rows) Postgres table on a regular and frequent
> basis. These processes often run for weeks at a time, but over the
Are these long
On Thu, Jul 14, 2005 at 03:08:30PM +1000, Alison Winters wrote:
> Hi,
>
> Our application requires a number of processes to select and update rows
> from a very small (<10 rows) Postgres table on a regular and frequent
> basis. These processes often run for weeks at a time, but over the
> space o
