> alter a table column to its own type, like this:
> alter table foo alter column my_counter type integer; -- my_counter
> is already an integer
Is that really reclaim disk space and how ??
For example; if 'my_counter' column is already integer,
why do I alter this column to integer again ?
Firstly, thanks for your explanations...
> Are you attempting a one-time space reduction or are you having general
> bloat issues?
Unfortunately, I have growing bloat issues so I want to reduce space as it
filled up.
Thus I wrote a script but as I said before it doesn't reclaim disk space.
command output for mentioned db : ' my_db_name | 42 GB '
I don't print query results to logfile. I restore my system logs to db.
I have a lot of live ( growing ) logs on my machine and I register these
logs to db.
My essential question is that why don't I reclaim disk space though I run
this com
My PostgreSQL version is 8.1.11.
My log entries are on filesytem and I write these logs to db from unix
stream.
Another interesting situation is that while my logs on filesystem contains
about 5-6 GB,
db directory (/base/OID) contains 40 GB. Is that normal ?
I implement your suggestions by usi
On 05/26/2010 07:50 AM, paladine wrote:
It is default value ( #checkpoint_segments = 3# in logfile segments, min
1, 16MB each )
Many of my database configurations are default values. (plain TOAST etc)
my database is a log database so, some tables of db grow everytime.
My ' /base ' directory
On 05/26/2010 07:16 AM, paladine wrote:
Hi all,
How can I reduce disk space postgresql used ?
I tried to delete many rows from my database and
I am running ' vacuum analyze reindexdb ' commands regularly
but my disk space on my linux machine didn't reduce.
I know that ' vacuum full ' command ca
On 26 May 2010 15:50, paladine wrote:
>
> It is default value ( #checkpoint_segments = 3 # in logfile segments, min
> 1, 16MB each )
> Many of my database configurations are default values. (plain TOAST etc)
> my database is a log database so, some tables of db grow everytime.
> My ' /base ' d
It is default value ( #checkpoint_segments = 3# in logfile segments, min
1, 16MB each )
Many of my database configurations are default values. (plain TOAST etc)
my database is a log database so, some tables of db grow everytime.
My ' /base ' directory contains a lot of compressed object (1GB
On Wed, May 26, 2010 at 10:16 AM, paladine wrote:
> Anyone know another method ?
>
options to reclaim disk space:
vacuum full
dump/restore (sometimes faster than vacuum full)
cluster (not mvcc safe as far as i know)
alter a table column to its own type, like this:
alter table foo alter column m
On 26 May 2010 15:16, paladine wrote:
>
> Hi all,
>
> How can I reduce disk space postgresql used ?
> I tried to delete many rows from my database and
> I am running ' vacuum analyze reindexdb ' commands regularly
> but my disk space on my linux machine didn't reduce.
>
> I know that ' vacuum full
Hi all,
How can I reduce disk space postgresql used ?
I tried to delete many rows from my database and
I am running ' vacuum analyze reindexdb ' commands regularly
but my disk space on my linux machine didn't reduce.
I know that ' vacuum full ' command can do that but I don't want to use
that
11 matches
Mail list logo
