Обсуждение: Autovacuum ro prevent wraparound

<div class="WordSection1"><p class="MsoNormal">I’m running PostgreSQL 8.4 on Ubuntu.  While Postgres was do three
autovacuums(to prevent wraparound) on three really large tables the root (/) directory filled to 100%.  The filesystem
forPostgres (/dev/mapper/db_vg-db_lv mounted on /db) has 56% of its space available.  While Postgres was running, as
soonas I’d free up some space in the root file system, some process would gobble it up.  I stopped the Postgres service
andimmediately 7.5 GB freed up in the root filesystem.<p class="MsoNormal"> <p class="MsoNormal">Does Postgres use disk
spaceoutside of its own filesystem/directory tree?  Is there a setting in the conf file so this can be directed to
anotherfilesystem (such as the /db)?  <p class="MsoNormal"> <p class="MsoNormal">Thanks,<p class="MsoNormal"> <p
class="MsoNormal">SteveErickson<p class="MsoNormal">Senior Developer<p class="MsoNormal"> <p class="MsoNormal">NOTICE: 
Thisemail, including any attachments, is covered by the Electronic Communications Privacy Act, is confidential and may
belegally privileged.  If you are not the intended recipient, you are hereby notified that any retention,
dissemination,distribution or copying of this communication is strictly prohibited.  If you have received this
communicationin error, please immediately notify our office by return email or at our telephone number (651) 925-3200. 
Thendelete and destroy all copies of this email and any attachments.<p class="MsoNormal"> <p class="MsoNormal">Thank
you.<pclass="MsoNormal"> </div> 

Since John hasn't responded, I will.

MacPorts base version 2.2.1 installed
port selfupdate from today (2014-01-15)

Steps to reproduce on OSX 10.8.5:

sudo port install pgadmin3 +postgresql93

open pgadmin

drill down to any table in any existing database in the tree view.
click on a table
click on the SQL icon in the toolbar
error message appears as John described
hit cancel and go on with life for the remainder of the process lifetime

I can also install pgAdmin3 +debug+postgresql93.  This gives an additional
error message when I click on the database name "cannot find resources ..... 
/*.xrc".   I click on OK and ignore this also.

IDK what else you need.  Please let me know and I'll make it happen and
attach it here.


/Kirk



--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Autovacuum-ro-prevent-wraparound-tp5785547p5787338.html
Sent from the PostgreSQL - pgadmin support mailing list archive at Nabble.com.

On Wed, Jan 15, 2014 at 10:06 PM, bithead <kirk@webfinish.com> wrote:
> Since John hasn't responded, I will.
>
> MacPorts base version 2.2.1 installed
> port selfupdate from today (2014-01-15)
>
> Steps to reproduce on OSX 10.8.5:
>
> sudo port install pgadmin3 +postgresql93
>
> open pgadmin
>
> drill down to any table in any existing database in the tree view.
> click on a table
> click on the SQL icon in the toolbar
> error message appears as John described
> hit cancel and go on with life for the remainder of the process lifetime
>
> I can also install pgAdmin3 +debug+postgresql93.  This gives an additional
> error message when I click on the database name "cannot find resources .....
> /*.xrc".   I click on OK and ignore this also.
>
> IDK what else you need.  Please let me know and I'll make it happen and
> attach it here.

It's an issue that should be fixed sometime, but it's technically just
an annoyance, not a problem. However, it's a debug assertion, so it
should only be appearing in a debug build. So the real issue here is
that MacPorts is building a debug binary?

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

>> MacPorts is building a debug binary? 
Maybe a debug binary of wxWidgets-3.0?  It only builds a pgadmin3 debug
binary if you tell it to with
sudo port install pgadmin3 +debug

>>but it's technically just an annoyance, not a problem...
True, it just means hitting cancel once on the first SQL window.   I guess
that's why it hasn't been reported before.

I was hoping it was just a nit that could be easily fixed.   No worries. 
Thanks



--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Autovacuum-ro-prevent-wraparound-tp5785547p5787470.html
Sent from the PostgreSQL - pgadmin support mailing list archive at Nabble.com.