Re: BUG #13847: WARNING: skipping "pg_toast_" --- cannot vacuum indexes, views, or special system tables VACUUM - Mailing list pgsql-bugs
| From | Navaneethakrishnan Gopal |
|---|---|
| Subject | Re: BUG #13847: WARNING: skipping "pg_toast_" --- cannot vacuum indexes, views, or special system tables VACUUM |
| Date | |
| Msg-id | 843307396.1094900.1452105412125.JavaMail.yahoo@mail.yahoo.com Whole thread Raw |
| In response to | Re: BUG #13847: WARNING: skipping "pg_toast_" --- cannot vacuum indexes, views, or special system tables VACUUM (Kevin Grittner <kgrittn@gmail.com>) |
| List | pgsql-bugs |
Hi Kevin,
Thanks a lot for getting back on this.
1) Customer is facing issue in our application running 8.2 version PG
linux# su postgres -s /bin/sh -c "postgres --version"
postgres (PostgreSQL) 8.2.3
postgres (PostgreSQL) 8.2.3
unicorn=# select version();
version
------------------------------------------------------------------------
PostgreSQL 8.2.3 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.4.3
(1 row)
version
------------------------------------------------------------------------
PostgreSQL 8.2.3 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.4.3
(1 row)
2) This is the current error customer is facing; which I think same as this https://wiki.postgresql.org/wiki/20110408pg_upgrade_fix#What_is_the_underlying_cause_of_this_bug.3F
700002 org.postgresql.util.PSQLException: ERROR: could not access status of transaction 192282624 Detail: Could not open file "pg_clog/00B7": No such file or directory. org.postgresql.util.PSQLException: ERROR: could not access status of transaction 192282624 Detail: Could not open file "pg_clog/00B7": No such file or directory. at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1548) ~[postgresql-8.2-504.jdbc3.jar:na] at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1316) ~[postgresql-8.2-504.jdbc3.jar:na] at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:191) ~[postgresql-8.2-504.jdbc3.jar:na] at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452) ~[postgresql-8.2-504.jdbc3.jar:na] at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:337) ~[postgresql-8.2-504.jdbc3.jar:na]
3) We tried applying the fix in two ways
3.i) Just copy and past the text from this page in the psql windown
3.ii) By running like this "psql -U postgres -a -f pg_upgrade_fix.sql unicorn >> error.txt 2>&1"
Have attached both "pg_upgrade_fix.sql" and error.txt with this mail
Please help us on solving these errors.
4) As this issue is already fixed in 9.4 version, we have our newer application which uses 9.4 PG. But customer currently can't migrate to this new
unicorn=# select version();
version
----------------------------------------------------------------------------------------------------------------------------------------
PostgreSQL 9.4.1 on x86_64-mv-linux-gnu, compiled by i686-montavista-linux-gnu-gcc (MontaVista Linux G++ 4.4-1311130628) 4.4.1, 64-bit
(1 row)
version
----------------------------------------------------------------------------------------------------------------------------------------
PostgreSQL 9.4.1 on x86_64-mv-linux-gnu, compiled by i686-montavista-linux-gnu-gcc (MontaVista Linux G++ 4.4-1311130628) 4.4.1, 64-bit
(1 row)
4.i) May be not applicable here, just to ensure the above script is working fine, we tried here in the 9.4 PG version. As expected we didn't see any error. Please check "no_error*.txt"
Could you please help us on solving the warning message seen (error.txt) in 8.2 PG version.
Please let us know if you require more info.
Thanks,
Navanee
From: Kevin Grittner <kgrittn@gmail.com>
To: gnkna@yahoo.co.in
Cc: "pgsql-bugs@postgresql.org" <pgsql-bugs@postgresql.org>
Sent: Wednesday, January 6, 2016 8:39 PM
Subject: Re: [BUGS] BUG #13847: WARNING: skipping "pg_toast_" --- cannot vacuum indexes, views, or special system tables VACUUM
On Tue, Jan 5, 2016 at 9:15 AM, <gnkna@yahoo.co.in> wrote:
> Postgres Version:8.2
Do you really mean 8.2, not 9.2? For a running instance, please
connect with psql (or similar) and give the output of:
SELECT version();
If you have installed software for an upgrade and don't have a
cluster running yet, please run the following at a command line and
show the results:
<path to executables>/postgres --version
Always use copy/paste for such things, rather than retyping or
showing what you think are the relevant parts.
> One of our customer is hitting this issue 20110408pg_upgrade_fix.
Rather than a diagnosis, please show exactly what you are doing and
what the results are. You certainly can't be hitting this bug if
you are upgrading from 8.2.
https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
> Customer currently cannot upgrade to our new software (which is
> running with 9.x PG DB).
Again, 9.x doesn't even tell us what the major release is. Copy
paste a full version, as described above.
> Sorry if this is an wrong alias? Could you please guide us to the
> correct mailing list.
This would be more appropriate on the pgsql-general list.
http://www.postgresql.org/list/
Please start a new thread there with the information suggested by
the "Guide to reporting problems" page referenced above. You can
do that by just sending an email to: pgsql-general@postgresql.org
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Attachment
pgsql-bugs by date: