On Wed, 2009-04-22 at 13:31 -0400, Tom Lane wrote:
> "Maria L. Wilson" writes:
> > Question - is there any maintenance type item that we could to to check
> > for uncommitted transactions on a regular basis - outside of the
> > pg_prepared_xacts table?
>
> pg_prepared_xacts is the only SQL-le
"Maria L. Wilson" writes:
> Question - is there any maintenance type item that we could to to check
> for uncommitted transactions on a regular basis - outside of the
> pg_prepared_xacts table?
pg_prepared_xacts is the only SQL-level visibility there is. From a
monitoring standpoint it might
On Wed, 2009-04-22 at 13:10 -0400, Maria L. Wilson wrote:
> wow - I am finally back in business!!
> Question - is there any maintenance type item that we could to to check
> for uncommitted transactions on a regular basis - outside of the
> pg_prepared_xacts table?
>How about from a dev
wow - I am finally back in business!!
Tom - the answer to your question is yes - these uncommitted
transactions blocked the vacuuming. As soon as i got around getting the
uncommitted transactions rollbacked - the vacuuming worked and things
seemed fine. One other little thing i had was a cor
Maria L. Wilson wrote:
> yes - how do i get rid of these??
>
> backend> select * from pg_prepared_xacts;
> 2009-04-22 07:43:27.421 EDT [11767] [] WARNING: database "ange" must
> be vacuumed within 976080 transactions
> 2009-04-22 07:43:27.421 EDT [11767] [] HINT: To avoid a database
> shu
"Maria L. Wilson" writes:
> yes - how do i get rid of these??
Either COMMIT PREPARED or ROLLBACK PREPARED, depending on whether
you think you want those old transactions to take effect or not.
(Personally I'd go for ROLLBACK --- if you did not even know those
transactions were open, you probably
yes - how do i get rid of these??
backend> select * from pg_prepared_xacts;
2009-04-22 07:43:27.421 EDT [11767] [] WARNING: database "ange" must
be vacuumed within 976080 transactions
2009-04-22 07:43:27.421 EDT [11767] [] HINT: To avoid a database
shutdown, execute a full-database VACUUM
"Maria L. Wilson" writes:
> i'm getting the following error. any ideas why this would be in
> single user mode??
Maybe you've got some prepared transactions laying about?
Check pg_prepared_xacts ...
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-adm
this is the command that i used to start the backend
postgres --single -D /data/pg_devices ange
Maria L. Wilson wrote:
i'm getting the following error. any ideas why this would be in
single user mode??
backend> drop database "scoogan_userprofile_1.2"
2009-04-21 18:18:23.032 EDT [
i'm getting the following error. any ideas why this would be in
single user mode??
backend> drop database "scoogan_userprofile_1.2"
2009-04-21 18:18:23.032 EDT [11767] [] WARNING: database "ange" must
be vacuumed within 976081 transactions
2009-04-21 18:18:23.032 EDT [11767] [] HINT:
10 matches
Mail list logo
