2008/3/26, Alvaro Herrera <[EMAIL PROTECTED]>:
> Clodoaldo escribió:
>
>
> > The database performance slowly degrades and after two weeks i issue a
> > reindex on the database and the performance gets back to normal. I
> > have been doing this for ages and i don't remember in which version
> >
Clodoaldo escribió:
> The database performance slowly degrades and after two weeks i issue a
> reindex on the database and the performance gets back to normal. I
> have been doing this for ages and i don't remember in which version
> this degradation behavior appeared, perhaps 8.0 I'm not sure.
W
2008/3/13, Alvaro Herrera <[EMAIL PROTECTED]>:
> Clodoaldo escribió:
>
> > 2008/3/13, Alvaro Herrera <[EMAIL PROTECTED]>:
> > > Clodoaldo escribió:
> > >
> > >
> > > > Now what is happening is that reindex does not finish even with a
> > > > small 6,500 rows table and after a reboot. In top
2008/3/14, Alvaro Herrera <[EMAIL PROTECTED]>:
> Clodoaldo escribió:
>
> > 2008/3/14, Alvaro Herrera <[EMAIL PROTECTED]>:
>
>
> > > A quick look into pg_locks should tell you if it's blocking.
> >
> > pg_prepared_xacts is empty and pg_locks has 288 rows:
> >
> > # select locktype, mode, count(
Clodoaldo escribió:
> 2008/3/14, Alvaro Herrera <[EMAIL PROTECTED]>:
> > A quick look into pg_locks should tell you if it's blocking.
>
> pg_prepared_xacts is empty and pg_locks has 288 rows:
>
> # select locktype, mode, count(*) as total
> from pg_locks group by locktype, mode;
>locktype
2008/3/14, Alvaro Herrera <[EMAIL PROTECTED]>:
> Clodoaldo escribió:
>
>
> > Postgresql was restarted twice, but yes, it is as if the crash left
> > some kind of permanent lock somewhere.
>
>
> A prepared transaction perhaps? SELECT * FROM pg_prepared_xacts;
>
> A quick look into pg_locks shoul
Clodoaldo escribió:
> Postgresql was restarted twice, but yes, it is as if the crash left
> some kind of permanent lock somewhere.
A prepared transaction perhaps? SELECT * FROM pg_prepared_xacts;
A quick look into pg_locks should tell you if it's blocking.
--
Alvaro Herrera
2008/3/14, Pavan Deolasee <[EMAIL PROTECTED]>:
> On Fri, Mar 14, 2008 at 5:19 AM, Clodoaldo
>
> <[EMAIL PROTECTED]> wrote:
>
> >
>
> > > Try vacuuming pg_class, pg_index, pg_attribute manually and see if that
> > > makes the problem go away.
> >
> > It does not go away.
> >
>
>
> Can it b
2008/3/14, Scott Marlowe <[EMAIL PROTECTED]>:
> On Thu, Mar 13, 2008 at 5:49 PM, Clodoaldo
> <[EMAIL PROTECTED]> wrote:
> > 2008/3/13, Alvaro Herrera <[EMAIL PROTECTED]>:
> > > Clodoaldo escribió:
> > >
> > > > 2008/3/13, Alvaro Herrera <[EMAIL PROTECTED]>:
> > > > > Clodoaldo escribió:
On Fri, Mar 14, 2008 at 5:19 AM, Clodoaldo
<[EMAIL PROTECTED]> wrote:
>
> > Try vacuuming pg_class, pg_index, pg_attribute manually and see if that
> > makes the problem go away.
>
> It does not go away.
>
Can it be a case where some other open transaction is holding a lock
on the table ? No
On Thu, Mar 13, 2008 at 5:49 PM, Clodoaldo
<[EMAIL PROTECTED]> wrote:
> 2008/3/13, Alvaro Herrera <[EMAIL PROTECTED]>:
> > Clodoaldo escribió:
> >
> > > 2008/3/13, Alvaro Herrera <[EMAIL PROTECTED]>:
> > > > Clodoaldo escribió:
> > > >
> > > >
> > > > > Now what is happening is that rei
2008/3/13, Alvaro Herrera <[EMAIL PROTECTED]>:
> Clodoaldo escribió:
>
> > 2008/3/13, Alvaro Herrera <[EMAIL PROTECTED]>:
> > > Clodoaldo escribió:
> > >
> > >
> > > > Now what is happening is that reindex does not finish even with a
> > > > small 6,500 rows table and after a reboot. In top
2008/3/13, Greg Smith <[EMAIL PROTECTED]>:
> On Thu, 13 Mar 2008, Clodoaldo wrote:
>
> > I recently had a crash during a bulk insert when i updated to the
> > 2.6.24.3-12.fc8 kernel. I rebooted and Postgresql did its thing to
> > recover and everything was working. I made the previous kernel,
>
Clodoaldo escribió:
> 2008/3/13, Alvaro Herrera <[EMAIL PROTECTED]>:
> > Clodoaldo escribió:
> >
> >
> > > Now what is happening is that reindex does not finish even with a
> > > small 6,500 rows table and after a reboot. In top there is no CPU or
> > > memory usage by postmaster and vmstat show
2008/3/13, Alvaro Herrera <[EMAIL PROTECTED]>:
> Clodoaldo escribió:
>
>
> > Now what is happening is that reindex does not finish even with a
> > small 6,500 rows table and after a reboot. In top there is no CPU or
> > memory usage by postmaster and vmstat shows no disk activity.
>
>
> Hmm, are
Clodoaldo escribió:
> Now what is happening is that reindex does not finish even with a
> small 6,500 rows table and after a reboot. In top there is no CPU or
> memory usage by postmaster and vmstat shows no disk activity.
Hmm, are you vacuuming the system catalogs appropriately?
--
Alvaro Herr
On Thu, 13 Mar 2008, Clodoaldo wrote:
I recently had a crash during a bulk insert when i updated to the
2.6.24.3-12.fc8 kernel. I rebooted and Postgresql did its thing to
recover and everything was working. I made the previous kernel,
2.6.23.15-137.fc8, the default in grub.conf and rebooted.
H
This is 8.2.6 in Fedora 8 and the same database with which there were
performance problems when migrating to 8.3. The migration was not
done. The thread was this:
http://archives.postgresql.org/pgsql-general/2008-01/msg00508.php
The database performance slowly degrades and after two weeks i issue
18 matches
Mail list logo
