On Tue, Apr 25, 2006 at 04:47:53PM -0500, Jason Minion wrote:
> Usually a dump is significantly smaller than a live database due to
> space taken up by indexes and discarded tuples from MVCC. If it's
> significantly smaller you may also want to take a look at your vacuuming
> procedure.
Between ex
PROTECTED]
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of mcelroy, tim
Sent: Tuesday, April 25, 2006 4:06 PM
To: 'pgsql-admin@postgresql.org'
Subject: Re: [ADMIN] dbsize & pg_dump
Please disregard this question. I'm using pg_dump -F
Title: dbsize & pg_dump
Please
disregard this question. I’m using
pg_dump –F c which compresses the data a it backs it up.
Tim
-Original
Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of mcelroy, tim
Sent: Tuesday, April 25, 2006 4:40
PM
To: 'pgsql-
Hi,
> Hm. I cannot see anything wrong with the source code for database_size.
> I notice though that it depends on vsnprintf, which is known to be buggy
> in some releases of Solaris. Did you use the patch suggested in the
> last entry of doc/FAQ_Solaris?
>
I can't find any infos about patches
Andreas Schmitz <[EMAIL PROTECTED]> writes:
> I don't know if dbsize a part of the admin business here. I couln't find any
> contact infos in the README or the source. I have a 7.3 on solaris 8. When I
> try to execute "SELECT database_size('newsdb');" I get the following error
> message:
> ERR
Would you want to talk to this person:
[EMAIL PROTECTED] from this page: http://webmail.postgresql.org/~petere/index.html
I'd be interested in finding out why you get this error though.
thank you.
~ Troy Campano ~
-Original Message-
From: Andreas Schmitz [mailto:[EMAIL PROTECTED]]
Se
