connection open takes time.
I can almost 100% reduce it when my database size is 30 MB only with 1.5
bloating.
> Date: Tue, 14 May 2013 10:54:04 -0600
> Subject: Re: [GENERAL] Vacuum problem
> From: scott.marl...@gmail.com
> To: msq...@live.com
> CC: pgsql-general@postgresql.org
>
Not saying you HAVE bloating there, saying you MIGHT.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
I am doing regular insertion/deletion on the same tables .. and running vacuum
in an hour...
I suspect there is bloating in my tables.. but how does bloating in pgcatalog
is happening is not clear...> Normally vacuum full is NOT required on a regular
basis. However, if
> you did something like
On Tue, May 14, 2013 at 7:27 AM, S H wrote:
>> I wonder if you've got a bloated pg catalog then. Certainly sounds
>> like it's a possibility.
>> So other than vacuuming when you recreate this, is the server working
>> hard? What is vacuum vacuuming when this happens (pg_stat_activity
>> should sho
> I wonder if you've got a bloated pg catalog then. Certainly sounds
> like it's a possibility.
> So other than vacuuming when you recreate this, is the server working
> hard? What is vacuum vacuuming when this happens (pg_stat_activity
> should show that)
Does vacuum full is required to avoid bloa
On 5/13/2013 7:10 PM, S H wrote:
My disk is utilized by many other components, thus do we have minimum
recommendation my postgres to have sufficient speed. Current
perfomance of my disk is around 1-5MB/sec. Is it sufficient?
how are you measuring this? thats painfully slow by today's standa
My disk is utilized by many other components, thus do we have minimum
recommendation my postgres to have sufficient speed. Current perfomance of my
disk is around 1-5MB/sec. Is it sufficient?
Is it slow and can be cause of slow vacuuming..
On Mon, May 13, 2013 at 8:37 AM, S H wrote:
>> What is the db server doing when this happens? What does top, vmstat,
>> iostat etc have to say about it?
>
> It is high end server with 96 GB of RAM , 16 core server, but there are many
> other application running, This db is used for monitoring the
since it's out of support.
>
I am migrating to new version, for new customers , but for old existing
customer, it would require significant time. Is there any workaround for the
same. Like improving some DB parameters.
> Date: Mon, 13 May 2013 08:25:30 -0600
> Subject: Re: [GENERAL] V
On Mon, May 13, 2013 at 8:05 AM, S H wrote:
> Hi,
>
> I have my database in which i am executing vacuuming running manually in one
> hour.
vacuum or vacuum full?
> In my production database sometime when vacuuming is running it is taking
> long time in opening connection.
What is the db server
Kari Lavikka <[EMAIL PROTECTED]> writes:
> However, database wide vacuum prevents user_online vacuum from deleting
> old row versions and the table gets incredibly bloated.
Update to 8.2. There was a fix put in for this specific issue.
regards, tom lane
On Tue, Dec 07, 2004 at 06:35:39PM -0700, Ed L. wrote:
> On Tuesday December 7 2004 6:27, Ed L. wrote:
> > On Tuesday December 7 2004 5:58, marcelo Cortez wrote:
> La traducción de Babelfish de mi mensaje anterior era hilarante, e indica
> que mi español es lejos peor que pensamiento de I.
Tends
On Tuesday December 7 2004 6:27, Ed L. wrote:
> On Tuesday December 7 2004 5:58, marcelo Cortez wrote:
> > > > /psql someDatabase
> > > > vaccum full verbose;
> > > > but nothing informs.
> > > > in which cases vacuum do not inform anything?
> > > > postgresql 7.4 on red hat 9.0
> > > > any clue
On Tuesday December 7 2004 5:58, marcelo Cortez wrote:
> >
> > > /psql someDatabase
> > > vaccum full verbose;
> > > but nothing informs.
> > > in which cases vacuum do not inform anything?
> > > postgresql 7.4 on red hat 9.0
> > > any clue be appreciate.
> > > best regards
> >
> > Is your server
mordicus <[EMAIL PROTECTED]> writes:
> vacuum verbose analyse record_blob;
> NOTICE: --Relation record_blob--
> NOTICE: Pages 62437: Changed 0, reaped 0, Empty 0, New 0; Tup 1005540: Vac
> 0, Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 80, MaxLen 2032; Re-using:
> Free/Avail. Space 0/0; EndEmpty/A
15 matches
Mail list logo
