Re: [BUGS] executing SELECT xmlelement(name foo); causes "server closed the connection unexpectedly" Error

I tried installing following RPMs postgresql-8.3.5-1PGDG.rhel5.x86_64.rpm postgresql-libs-8.3.5-1PGDG.rhel5.x86_64.rpm postgresql-server-8.3.5-1PGDG.rhel5.x86_64.rpm still this issue is appearing. is there any thing i am missing? Please advise. Thanks, Peter Eisentraut wrote: > Sushil wrote:

Re: [BUGS] could not read block 77 of relation 1663/16385/388818775

Heikki Linnakangas <[EMAIL PROTECTED]> writes: > Craig Ringer wrote: >> Is there any chance you have EVER hard-killed the postmaster manually >> (eg with "kill -9" or "kill -KILL")? > There is safeguards against that. If postmaster dies, the backends > should die quickly and gracefully too. And p

Re: [BUGS] could not read block 77 of relation 1663/16385/388818775

Craig Ringer wrote: Is there any chance you have EVER hard-killed the postmaster manually (eg with "kill -9" or "kill -KILL")? If you do that and don't also kill the backends, it's my understanding that BAD things may happen especially if you then attempt to relaunch the postmaster. There is sa

Re: [BUGS] could not read block 77 of relation 1663/16385/388818775

Alexandra Nitzschke wrote: > Hi, > > we have had similar postgres problems in the past. > Please have a look at Bug 3484. > > We didn't resolve the problems metioned in bug 3484. The other postgres > developers also thought, that there are hardware > problems. > So our customer bought a new serve

Re: [BUGS] could not read block 77 of relation 1663/16385/388818775

Hi, we have had similar postgres problems in the past. Please have a look at Bug 3484. We didn't resolve the problems metioned in bug 3484. The other postgres developers also thought, that there are hardware problems. So our customer bought a new server with diffrent hardware configuration ( ..

Re: [BUGS] BUG #4529: lc_messages in config ignored

Hello Bruce, Thursday, November 20, 2008, 3:20:42 PM, you wrote: BM> Rainer Bauer wrote: >> I have reported this bug about a month ago: >> but never >> got >> any response. BM> Yep, we know it is a bug but haven't found a fix yet.

Re: [BUGS] executing SELECT xmlelement(name foo); causes "server closed the connection unexpectedly" Error

Sushil wrote: I am trying to exploit XML features of PostgreSQL 8.3.0 DB. You should upgrade to the latest 8.3 release, currently 8.3.5. There were some fixes in this area (and other areas). -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscriptio

Re: [BUGS] BUG #4529: lc_messages in config ignored

Rainer Bauer wrote: > "pro" wrote: > > >The following bug has been logged online: > > > >Bug reference: 4529 > >Logged by: pro > >Email address: [EMAIL PROTECTED] > >PostgreSQL version: 8.3.* > >Operating system: windows xp sp2 eng + rus mui > >Description:lc_messages

[BUGS] executing SELECT xmlelement(name foo); causes "server closed the connection unexpectedly" Error

Hi, I am trying to exploit XML features of PostgreSQL 8.3.0 DB. I tried executing following query: SELECT xmlelement(name foo); from psql prompt. I received Following error on screen: server closed the connection unexpectedly This probably means the server terminated abnormally

Re: [BUGS] BUG #4539: to_char(to_timestamp('...','....')) returns the wrong result

Stuart Green wrote: select to_char(to_timestamp('2008-11-14 16:00:00','-MM-DD HH24:MM:SS'),'day'); is returning monday as the day in all the dbase version I Have test, 8.2.11, 8.2.10, and 8.1.11 Use 'MI' instead of 'MM' for the minutes. to_timestamp is quite lenient, and interpretes the 0

Re: [BUGS] could not read block 77 of relation 1663/16385/388818775

Alexandra Nitzschke wrote: > Hi, > > we encountered the following error while inserting a record into a table: > > org.postgresql.util.PSQLException: ERROR: could not read block 77 of > relation 1663/16385/388818775: read only 0 of 8192 bytes > > Using postgres 8.3.5 > > The reported object is

Re: [BUGS] could not read block 77 of relation 1663/16385/388818775

Alexandra Nitzschke wrote: Hi, we encountered the following error while inserting a record into a table: org.postgresql.util.PSQLException: ERROR: could not read block 77 of relation 1663/16385/388818775: read only 0 of 8192 bytes This is probably a problem with your disk or filesystem. Have

[BUGS] could not read block 77 of relation 1663/16385/388818775

Hi, we encountered the following error while inserting a record into a table: org.postgresql.util.PSQLException: ERROR: could not read block 77 of relation 1663/16385/388818775: read only 0 of 8192 bytes Using postgres 8.3.5 The reported object is an index. The size of its data file is 63078

Re: [BUGS] substring with this pattern works in 8.3.1; does not work in 8.3.4

On 2008-11-12 19:07, Chris Wood wrote: > here is where it works in 8.3.1: > CONSTRAINT public_phone_ch CHECK (((public_phone = ''::text) OR > ("substring"(public_phone, '^[0-9]{10}(,[0-9]{10})*$'::text) IS NOT NULL; > protocalte=> insert into locn values(10, '1231231234') ; 8.3.1 had a bu

[BUGS] BUG #4539: to_char(to_timestamp('...','....')) returns the wrong result

The following bug has been logged online: Bug reference: 4539 Logged by: Stuart Green Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.11 Operating system: Centos 5 Description:to_char(to_timestamp('...','')) returns the wrong result Details: The query