On 21/07/10 20:21, paladine wrote:
>
> I have a linux daemon that parses some datas and writes to db continuously
> but my db is growing unexpectedly so I must reduce disk space once a week.
I assume you're also deleting from the database, given that its growth
is a problem.
It sounds like you n
yasinma...@gmail.com (paladine) writes:
> Hi all
> I prefer doing pg_dump - psql restore to vacuum full and
> is there anyone know whether postgresql can insert data concurrently while
> restoring a table for not losing any data.
>
> thanks in advance...
The problem scenario that I'd expect is w
I have a linux daemon that parses some datas and writes to db continuously
but my db is growing unexpectedly so I must reduce disk space once a week.
vacuum full is one solution but pg_dump-restore gives back more space to OS.
I wrote a script like this
# pg_dump db > asd.sql (1)
# dropdb db
On 21/07/10 19:26, paladine wrote:
>
> Hi all
> I prefer doing pg_dump - psql restore to vacuum full and
> is there anyone know whether postgresql can insert data concurrently while
> restoring a table for not losing any data.
There's no particular reason why you can't just feed a data-only dum
Hi all
I prefer doing pg_dump - psql restore to vacuum full and
is there anyone know whether postgresql can insert data concurrently while
restoring a table for not losing any data.
thanks in advance...
--
View this message in context:
http://old.nabble.com/pg_dump-restore-concurrency-tp29224
