[BUGS] Reltuples/n_live_tup values wrong

2013-08-07 Thread Sebastian Kornehl
Hi, I'm facing a problem which seems like a bug to me. I'm running: centos 5.9 postgresql92.x86_64 (9.2.4-1PGDG.rhel5) I have a table whith many inserts/deletes select * from pg_stat_user_tables where schemaname = 'lobby' and relname = 'lobby_player' order by n_live_tup desc; relid | schemana

Re: [BUGS] Reltuples/n_live_tup values wrong

2013-08-07 Thread Tom Lane
Sebastian Kornehl writes: > I'm facing a problem which seems like a bug to me. I'm running: It seems like most of your problem is explained by this: >> DETAIL: 609299 dead row versions cannot be removed yet. You need to get rid of whatever old open transaction is preventing those rows from get

Re: [BUGS] Reltuples/n_live_tup values wrong

2013-08-07 Thread Sebastian Kornehl
Hi Tom, thanks for your Reply! You might be right, I found some pg_prepared_xacts from 2013-05-23. This was a test with a XA using application, but the application is already offline. There is also no pid available for the given transaction id's. Do you have any idea how to close these xa tr

Re: [BUGS] Reltuples/n_live_tup values wrong

2013-08-07 Thread Greg Stark
On Wed, Aug 7, 2013 at 1:50 PM, Sebastian Kornehl wrote: > Do you have any idea how to close these xa transactions without restarting > the whole db? Restarting the database wouldn't accomplish anything. Prepared transactions are persistent across reboots. http://www.postgresql.org/docs/9.3/sta

Re: [BUGS] Reltuples/n_live_tup values wrong

2013-08-07 Thread Tom Lane
Sebastian Kornehl writes: > You might be right, I found some pg_prepared_xacts from 2013-05-23. This > was a test with a XA using application, but the application is already > offline. There is also no pid available for the given transaction id's. > Do you have any idea how to close these xa tr

Re: [BUGS] Reltuples/n_live_tup values wrong

2013-08-07 Thread Sebastian Kornehl
Thank you, that did it! On 08/07/2013 03:30 PM, Tom Lane wrote: Sebastian Kornehl writes: You might be right, I found some pg_prepared_xacts from 2013-05-23. This was a test with a XA using application, but the application is already offline. There is also no pid available for the given transa

[BUGS] BUG #8373: can create database with long name , but can't connect

2013-08-07 Thread gerrit . geurs
The following bug has been logged on the website: Bug reference: 8373 Logged by: Gerrit Geurs Email address: gerrit.ge...@hp.com PostgreSQL version: 9.2.4 Operating system: RHEL 6.4 Description: template1=# CREATE DATABASE vergunnigen_sit; CREATE DATABASE template1=#

Re: [BUGS] BUG #8373: can create database with long name , but can't connect

2013-08-07 Thread Pavan Deolasee
On Wed, Aug 7, 2013 at 8:14 PM, wrote: > The following bug has been logged on the website: > > Bug reference: 8373 > Logged by: Gerrit Geurs > Email address: gerrit.ge...@hp.com > PostgreSQL version: 9.2.4 > Operating system: RHEL 6.4 > Description: > > template1=# CREATE DAT

Re: [BUGS] BUG #8373: can create database with long name , but can't connect

2013-08-07 Thread Alvaro Herrera
gerrit.ge...@hp.com wrote: > template1=# CREATE DATABASE vergunnigen_sit; > CREATE DATABASE > template1=# GRANT ALL PRIVILEGES ON DATABASE vergunnigen_sit to postgres; > GRANT > template1=# \q > -bash-4.1$ psql vergunningen_sit > psql: FATAL: database "vergunningen_sit" does not exist > > > Whe

Re: [BUGS] BUG #8335: trim() un-document behaviour

2013-08-07 Thread Bruce Momjian
On Fri, Jul 26, 2013 at 02:23:10AM +, am...@amutu.com wrote: > in the postgresql doc 9.4,I find the trim() function like this: > > > trim([leading | trailing | both] [characters] from string) > > > so the trim should be pass only one argument with some optional prefix --- > but I > find th