Re: Re: a "huge" table with small rows and culumns

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Feng Xue" <feng(at)axe(dot)net(dot)au>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Re: a "huge" table with small rows and culumns
Date: 2000-12-18 23:31:05
Message-ID: 2290.977182265@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Feng Xue" <feng(at)axe(dot)net(dot)au> writes:
> Actually this table is accessed by JDBC from a Jonas EJB entity bean. and it is constantly looked
> up, and after I
> use "ls -al" I can find that in /usr/local/pgsql/data/base/The_data_base_name/The_huge_table
> timestamp is updated as the user access that table. I have no idea why the timestamp is keeping
> updated and the size is keeping growing even through there are no updateing and the rows are only
> 50.

Clearly, the table *is* being updated, whether you think it is or not.
You might want to check to see just what queries that bean is really
issuing. One way to do that is to restart the postmaster with -d2
and look to see what queries get logged. (Don't forget to redirect
the postmaster's stdout/stderr to some appropriate log file, and do
*not* use -S in the postmaster switches.)

Another possible source of unexpected updates is forgotten rules or
triggers.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Sandeep Joshi 2000-12-19 00:12:32 Trigger question
Previous Message Tulio Oliveira 2000-12-18 23:26:07 Re: Re: check constraint