[HACKERS] pg_autovacuum and v8.0

2004-09-09 Thread Herv Piedvache
Hi,

I was thinking that new things will appear in v8.0 about pg_autovacuum ??

But I find nothing new in README and/or Version History 

Any help ?

Regards,
-- 
Hervé Piedvache

Elma Ingénierie Informatique
6 rue du Faubourg Saint-Honoré
F-75008 - Paris - France
Pho. 33-144949901
Fax. 33-144949902

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html


Re: [HACKERS] pg_autovacuum and v8.0

2004-09-09 Thread Herv Piedvache
OK thanks !

Le Jeudi 9 Septembre 2004 18:14, Thomas F.O'Connell a écrit :
 pg_autovacuum will still be in contrib as of 8.0. It did not make
 integration with the core distribution.

 -tfo

 On Sep 9, 2004, at 11:09 AM, Hervé Piedvache wrote:
  Hi,
 
  I was thinking that new things will appear in v8.0 about pg_autovacuum
  ??
 
  But I find nothing new in README and/or Version History 
 
  Any help ?
 
  Regards,
  --
  Hervé Piedvache
 
  Elma Ingénierie Informatique
  6 rue du Faubourg Saint-Honoré
  F-75008 - Paris - France
  Pho. 33-144949901
  Fax. 33-144949902

-- 
Hervé Piedvache

Elma Ingénierie Informatique
6 rue du Faubourg Saint-Honoré
F-75008 - Paris - France
Pho. 33-144949901
Fax. 33-144949902

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])


[HACKERS] vacuum log are difficult to read ...

2004-03-12 Thread Herv Piedvache
Hi,

I know that we have more and more details to show, during vacuum analyze ... 
but since v7.4.x it's not really easy to read quicly a vacuum analyze to see 
important points ... like elapsed time or number of tupples deleted...

I would like to know first if you could make an effort about this ... only for 
human use ... ;o)
And also if it's possible to have a report of the abnormal situations ... may 
be something like the point I had once, with the number of pages for the 
table really cheaper than the pages of my index for the same table ...

Is it possible in a vacuum also to get informations about the quality of the 
parameters of the database .. for example the size of some parameters that 
are not in adequation with the data (pages, size of index etc.) we have in 
reality ... I don't know if my request is possible, but if so it could be a 
good opportunity for some tuning points, isn't it ?

I hope I'm clear with my demand ;o)

Regards,
-- 
Hervé Piedvache

Elma Ingénierie Informatique
6 rue du Faubourg Saint-Honoré
F-75008 - Paris - France
Pho. 33-144949901
Fax. 33-144949902

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
  subscribe-nomail command to [EMAIL PROTECTED] so that your
  message can get through to the mailing list cleanly


[HACKERS] Failed to initialize lc_messages 7.3b5

2002-11-07 Thread Herv Piedvache
Hi,

I don't know if it's important or not ... but on my linux Debian woody, with 
fr_FReuro parameter when I do the initdb I've got a creating template1 
database in /usr/local/pgsql/data/base/1... Failed to initialize lc_messages 
to ''

I just would like to know what that's mean exactly ...

Exact message of initdb :

 /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
The files belonging to this database system will be owned by user postgres.
This user must also own the server process.

The database cluster will be initialized with locale fr_FReuro.
This locale setting will prevent the use of indexes for pattern matching
operations.  If that is a concern, rerun initdb with the collation order
set to C.  For more information see the Administrator's Guide.

Fixing permissions on existing directory /usr/local/pgsql/data... ok
creating directory /usr/local/pgsql/data/base... ok
creating directory /usr/local/pgsql/data/global... ok
creating directory /usr/local/pgsql/data/pg_xlog... ok
creating directory /usr/local/pgsql/data/pg_clog... ok
creating template1 database in /usr/local/pgsql/data/base/1... Failed to 
initialize lc_messages to ''
ok
creating configuration files... ok
initializing pg_shadow... ok
enabling unlimited row size for system tables... ok
initializing pg_depend... ok
creating system views... ok
loading pg_description... ok
creating conversions... ok
setting privileges on built-in objects... ok
vacuuming database template1... ok
copying template1 to template0... ok

Success. You can now start the database server using:

    /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
or
    /usr/local/pgsql/bin/pg_ctl -D /usr/local/pgsql/data -l logfile start

regards,
-- 
Hervé Piedvache

Elma Ingénierie Informatique
6 rue du Faubourg Saint-Honoré
F-75008 - Paris - France
Tel. 33-144949901
fax. 33-144949902

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html