Postgres GOD wrote: > > i know this one is easy one to those postgres guru. > > how can i deal with this vacuum problem? > > NOTICE: CreatePortal: portal <vacuum> already exists > ERROR: can't create lock file -- another vacuum cleaner running? > > thanks. > > samil. > 'winning w/o fighting is best!'-suntzu. AFAIK there should be a file called "pg_vlock" in your Database-Dir, which you just have to delete. This always happens when a VACUUM is stopped unclean (i.e. postgres gets killed, etc.)
- [ADMIN] configuring pg_hba.conf... Postgres GOD
- Re: [ADMIN] configuring pg_hba.conf... Oliver Elphick
- Re: [ADMIN] configuring pg_hba.conf... Postgres GOD
- Re: [ADMIN] configuring pg_hba.conf... Oliver Elphick
- Re: [ADMIN] configuring pg_hba.conf... Carl Zmola
- [ADMIN] vacuum problem... Postgres GOD
- [ADMIN] maximum attribute record. Fischl Anton
- [ADMIN] maximum attribute record. Postgres GOD
- Re: [ADMIN] maximum attribute record. Vikrant Rathore
- Re: [ADMIN] maximum attribute record. Jan Kim
- Re: [ADMIN] maximum attribute record... Bruce Momjian
- Re: [HACKERS] Re: [ADMIN] maximu... Tom Lane
- Re: [ADMIN] maximum attribute record... Bruce Momjian