Re: [GENERAL] Fwd: I could not see any row in audit table

2017-01-25 Thread Shailesh Singh
2017 at 7:56 PM, Adrian Klaver wrote: > On 01/25/2017 03:03 AM, Shailesh Singh wrote: > >> >> >> >> Dear Group Member , >> >> >> I had configured the audit trigger for my datbase following the below >> document url: >> >> *https://

[GENERAL] Fwd: I could not see any row in audit table

2017-01-25 Thread Shailesh Singh
statement_only BOOLEAN NOT NULL); Now this table contains 50 GB of data , But when taking its backup using pg_dump and after restoring , it show that it has zero row. How to see the restored data? -- With Regards! Shailesh Singh

Re: [HACKERS] [GENERAL] Urgent Help Required

2013-10-08 Thread shailesh singh
yes i am executing psql to connect to this database. su - postgres psql patnadbold On Tue, Oct 8, 2013 at 8:48 PM, bricklen wrote: > > > > On Tue, Oct 8, 2013 at 8:13 AM, shailesh singh wrote: > >> >> On Tue, Oct 8, 2013 at 8:36 PM, bricklen wrote: >&g

Re: [GENERAL] Urgent Help Required

2013-10-08 Thread shailesh singh
33011 DETAIL: could not open file "pg_clog/": No such file or directory exit After this i am able to stop /start my db server but i am not able to connect to my databases (it tells to run vacuum full first on patnadbold databases) 1)I am using postgres 8.4 version. 2) I had t

[GENERAL] Urgent Help Required

2013-10-08 Thread shailesh singh
To avoid a database shutdown, execute a full-database VACUUM in "debug". WARNING: database "debug" must be vacuumed within 84 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "debug". WARNING: database "debug" must be vacuumed within 83 transactions HINT: To avoid a database shutdown, execute a full-database VACUUM in "debug". ERROR: could not access status of transaction 449971277 DETAIL: could not open file "pg_clog/01AD": No such file or directory Now what? Thanks in advance. Shailesh Singh