To all,
I just applied the v8.2.7 upgrade (from v8.2.6) on and FC8 server via
yum. The upgrade went OK, but the /var/lib/pgsql directory (with the
existing data) was renamed to /var/lib/pgsql.old and a new (and empty)
/var/lib/pgsql directory was created.
Does anyone know why this would ha
Sorry for the HTML posting previously.
I've already renamed the directories and the database is up and running.
I was just wondering if anyone else had this issue and what the reason, if
known, for the renaming. I completely understand this type of behavior when
doing a major version upgrade
On Thu, May 15, 2008 at 6:54 AM, alma korte <[EMAIL PROTECTED]> wrote:
> Dear list,
>
> I have the following issue with recovering disc space...
>
> Interscan Web Security Suite(Trend Micro gateway antivirus appl.) uses
> Postgres database to store access logs(to the internet) in table tb_url_usage
On Wed, May 14, 2008 at 7:33 PM, Duan Ligong <[EMAIL PROTECTED]> wrote:
>
> Hi, all
>
> Is there a way to estimate the size of the space which a postgresql database
> occupies? or the max size of db?
>
> I know there are a lot of factors, such as the frequency
> of updating, data size, which affect
Hi, Scott
Thanks for your reply.
There's also the old fashioned way:
I mean I want to estimate the size of the space which the db will occupy.
Now there is no db.
sudo su - postgres
cd $PGDATA # or wherever you point with -D on startup
du -sh .
Regards
Duan
--
Duan Ligong
TEL : 0561-7
Duan Ligong wrote:
I mean I want to estimate the size of the space which the db will occupy.
Now there is no db.
With a bit of math and the info here -
http://www.postgresql.org/docs/8.3/interactive/storage-page-layout.html
you can start to get an idea.
Simple calculation would be 23 bytes ove