On Mon, May 19, 2008 at 08:38:09PM +0200, Scott Marlowe wrote:
> OK. Assuming that the 50G is mostly dead space, there are a few
> possibilities that could be biting you here, but the most likely one
> is that your Free Space Map settings aren't high enough to include all
> the rows that have been
On Mon, May 19, 2008 at 5:44 PM, Dragan Zubac <[EMAIL PROTECTED]> wrote:
> Hello
>
> I have some similar situation like Yours,we're using at the moment PG 8.2.0.
As Gregory above mentioned, update NOW to 8.2.7. It only takes minutes to do.
> At the moment we do manually vacuum (one or more times
bject: Re: [GENERAL] Vacuuming on heavily changed databases
> Hello
>
> I have some similar situation like Yours,we're using at the moment PG
> 8.2.0.
<...>
Hello
I have some similar situation like Yours,we're using at the moment PG
8.2.0. At the moment we do manually vacuum (one or more times to
minimize 'dead' data/tuples),and if necessary we do 'full' vacuum. On
heavy-updated PG,one surely must think of this procedures because they
are conside
On Mon, May 19, 2008 at 8:50 AM, Bohdan Linda <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I would like to ask an opinion on vacuuming general. Imagine situation
> that you have single table with 5 fields (one varchar). This table has
> during the day
>
> - cca 620 000 inserts
> - 0 updates
> - cca 620
On Mon, May 19, 2008 at 06:21:18PM +0100, Sam Mason wrote:
> for t in foo bar baz
> do ( while echo "VACUUM $t;" && false ; do true ; done | psql ) &
> done
oops, that "&& false" shouldn't be there! like like this:
for t in foo bar baz
do ( while echo "VACUUM $t;" ; do true ; done |
On Mon, May 19, 2008 at 04:59:42PM +0200, Harald Armin Massa wrote:
> On Mon, May 19, 2008 at 04:50:18PM +0200, Bohdan Linda wrote:
> > I would like to ask an opinion on vacuuming general. Imagine situation
> > that you have single table with 5 fields (one varchar). This table has
> > during the da
On Mon, May 19, 2008 at 04:59:42PM +0200, Harald Armin Massa wrote:
> do not vacuum DAILY. set up autovacuum to run AT LEAST every minute.
> autovacuum will flag the "deleted" rows as to be reusable by next
> insert. Make sure to use 8.3., it's much more easy to setup
> autovacuum then before.
Hel
Apart from reinterating what someone else: you're not vacuuming
anywhere near often often. Normal vacuum takes no locks.
On Mon, May 19, 2008 at 04:50:18PM +0200, Bohdan Linda wrote:
> 3) There were suggestions (in archives) doing dump and then restore on
> dropped database, but still requires dow
Hello,
> I would like to ask an opinion on vacuuming general. Imagine situation
> that you have single table with 5 fields (one varchar). This table has
> during the day
>
> - cca 620 000 inserts
> - 0 updates
> - cca 620 000 deletes
>
> The table is vacuumed daily, but somehow after several month
Hello,
I would like to ask an opinion on vacuuming general. Imagine situation
that you have single table with 5 fields (one varchar). This table has
during the day
- cca 620 000 inserts
- 0 updates
- cca 620 000 deletes
The table is vacuumed daily, but somehow after several months I got to
size
11 matches
Mail list logo
