Re: [GENERAL] ERROR: could not open relation with OID 2836

2008-06-25 Thread Rodrigo Gonzalez
Tom Lane wrote: > Rodrigo Gonzalez <[EMAIL PROTECTED]> writes: >> Dont know exactly what you mean, if you are talking about the moment >> that I receive the error... > > No, it's clear that things are already broken before pg_dump started. > You need to show us how to get to this state from a fres

Re: [GENERAL] limits?

2008-06-25 Thread Robert Treat
On Monday 23 June 2008 15:45:22 Kynn Jones wrote: > On Mon, Jun 23, 2008 at 2:21 PM, Steve Atkins <[EMAIL PROTECTED]> wrote: > > In real use you're unlikely to hit any limits, theoretical or practical, > > but if you start to use a silly number of tables and so on you're likely > > to hit performan

Re: [GENERAL] ERROR: could not open relation with OID 2836

2008-06-25 Thread Tom Lane
Rodrigo Gonzalez <[EMAIL PROTECTED]> writes: > Dont know exactly what you mean, if you are talking about the moment > that I receive the error... No, it's clear that things are already broken before pg_dump started. You need to show us how to get to this state from a fresh database.

Re: [GENERAL] ERROR: could not open relation with OID 2836

2008-06-25 Thread Rodrigo Gonzalez
Tom Lane wrote: > Rodrigo Gonzalez <[EMAIL PROTECTED]> writes: >> Basically I should reinstall again PG with the same configuration and >> wait 1 night. Any log you need or want? anything to do besides doing the >> same I did? > > Umm ... if I reinstall PG and wait one night, I'm quite sure that >

Re: [GENERAL] ERROR: could not open relation with OID 2836

2008-06-25 Thread Tom Lane
Rodrigo Gonzalez <[EMAIL PROTECTED]> writes: > Basically I should reinstall again PG with the same configuration and > wait 1 night. Any log you need or want? anything to do besides doing the > same I did? Umm ... if I reinstall PG and wait one night, I'm quite sure that nothing much will happen.

Re: [GENERAL] ERROR: could not open relation with OID 2836

2008-06-25 Thread Rodrigo Gonzalez
Tom Lane wrote: > Rodrigo Gonzalez <[EMAIL PROTECTED]> writes: >> Craig Ringer wrote: >>> What platform are you using? > >> It's running under CentOS 4.4 using ext3, no RAID or LVM. >> Server is quad xeon 64 bits 3 GHz > > Ugh, I'd have liked to think RHEL4/Centos4 would be more reliable than > t

Re: [GENERAL] ERROR: could not open relation with OID 2836

2008-06-25 Thread Rodrigo Gonzalez
Tom Lane wrote: > Rodrigo Gonzalez <[EMAIL PROTECTED]> writes: >> Tom Lane wrote: >>> Did you update anything else at the same time? > >> No, just postgres was updated > > Well, that does start to sound like it could be a PG bug; but no one > else is reporting anything like it. Can you put toget

Re: [GENERAL] ERROR: could not open relation with OID 2836

2008-06-25 Thread Rodrigo Gonzalez
Tom Lane wrote: > Rodrigo Gonzalez <[EMAIL PROTECTED]> writes: >> It had been working with pgsql 8.1 and 8.2 for 2 years without problems. >> Suspicious is that problems started next day I've upgraded to 8.3. > > Did you update anything else at the same time? > > regards, to

Re: [GENERAL] ERROR: could not open relation with OID 2836

2008-06-25 Thread Tom Lane
Rodrigo Gonzalez <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> Did you update anything else at the same time? > No, just postgres was updated Well, that does start to sound like it could be a PG bug; but no one else is reporting anything like it. Can you put together a self-contained test cas

Re: [GENERAL] ERROR: could not open relation with OID 2836

2008-06-25 Thread Tom Lane
Rodrigo Gonzalez <[EMAIL PROTECTED]> writes: > It had been working with pgsql 8.1 and 8.2 for 2 years without problems. > Suspicious is that problems started next day I've upgraded to 8.3. Did you update anything else at the same time? regards, tom lane -- Sent via pgsql

Re: [GENERAL] ERROR: could not open relation with OID 2836

2008-06-25 Thread Tom Lane
Rodrigo Gonzalez <[EMAIL PROTECTED]> writes: > Craig Ringer wrote: >> What platform are you using? > It's running under CentOS 4.4 using ext3, no RAID or LVM. > Server is quad xeon 64 bits 3 GHz Ugh, I'd have liked to think RHEL4/Centos4 would be more reliable than that :-(. Still, you might hav

Re: [GENERAL] IF ROW( NEW ) <> ROW( OLD )

2008-06-25 Thread Tom Lane
"Richard Broersma" <[EMAIL PROTECTED]> writes: > I could manually expand the composite type OLD and NEW to enumerate > each field and make a row wise comparison. However, I was hoping to > avoid that. I think IF ROW(NEW.*) <> ROW(OLD.*) will work in recent releases. Actually you'd better use IF

Re: [GENERAL] what are rules for?

2008-06-25 Thread Tom Lane
"Michael Shulman" <[EMAIL PROTECTED]> writes: > On Tue, Jun 24, 2008 at 11:08 AM, Tom Lane <[EMAIL PROTECTED]> wrote: >> ... But updates and deletes require a >> pre-existing target tuple, and there just aren't any of those in a view >> relation. (Another way to say it is that update/delete requir

Re: [GENERAL] Serialized Access

2008-06-25 Thread Scott Marlowe
On Wed, Jun 25, 2008 at 9:21 AM, Phillip Mills <[EMAIL PROTECTED]> wrote: > I'm working on an application that uses EJB3 entities in JBoss, with > Hibernate and a PostgreSQL database. One of the entity tables needs > consistent, synchronized updates to rows in an environment where telling the > us

Re: [GENERAL] ERROR: could not open relation with OID 2836

2008-06-25 Thread Rodrigo Gonzalez
Tom Lane wrote: > Rodrigo Gonzalez <[EMAIL PROTECTED]> writes: >> PgSQL is returning that error when I open pgdmin and when I run some >> queries related to pg_buffercache. Also pg_dump cannot dump the DB. >> PgSQL version is 8.3.3 and happened one day after loading the DB there. > > That raises a

Re: [GENERAL] ERROR: could not open relation with OID 2836

2008-06-25 Thread Rodrigo Gonzalez
Craig Ringer wrote: > Rodrigo Gonzalez wrote: >> PgSQL is returning that error when I open pgdmin and when I run some >> queries related to pg_buffercache. Also pg_dump cannot dump the DB. >> >> PgSQL version is 8.3.3 and happened one day after loading the DB there. > > What platform are you using

Re: [GENERAL] IF ROW( NEW ) <> ROW( OLD )

2008-06-25 Thread Richard Broersma
On Wed, Jun 25, 2008 at 4:40 PM, Joshua D. Drake <[EMAIL PROTECTED]> wrote: > I have never tried it but you may be able to do it with a composite > type. True. However, I was under the impression that table types were essentially composite types. So I thought that composite types would behave th

Re: [GENERAL] ERROR: could not open relation with OID 2836

2008-06-25 Thread Tom Lane
Rodrigo Gonzalez <[EMAIL PROTECTED]> writes: > PgSQL is returning that error when I open pgdmin and when I run some > queries related to pg_buffercache. Also pg_dump cannot dump the DB. > PgSQL version is 8.3.3 and happened one day after loading the DB there. That raises a lot of questions about t

Re: [GENERAL] Serialized Access

2008-06-25 Thread Craig Ringer
Phillip Mills wrote: > I'm working on an application that uses EJB3 entities in JBoss, with > Hibernate and a PostgreSQL database. One of the entity tables needs > consistent, synchronized updates to rows in an environment where telling the > user that their operation failed and starting over is n

Re: [GENERAL] ERROR: could not open relation with OID 2836

2008-06-25 Thread Craig Ringer
Rodrigo Gonzalez wrote: > PgSQL is returning that error when I open pgdmin and when I run some > queries related to pg_buffercache. Also pg_dump cannot dump the DB. > > PgSQL version is 8.3.3 and happened one day after loading the DB there. What platform are you using? If Windows: - Which vers

Re: [GENERAL] a question about data corruption

2008-06-25 Thread Tom Lane
"Jacek Rembisz" <[EMAIL PROTECTED]> writes: > Postgresql started to log "could not access status of transaction" > messages. Since the transaction IDs were far away from what > server was using I took a look at data files i pgsql/base/ and I found > a total garbage there. > In five tables (of abo

[GENERAL] IF ROW( NEW ) <> ROW( OLD )

2008-06-25 Thread Richard Broersma
Is it possible to "cast" a table type to a ROW so that Row-Wise comparison can be achieved? -- Regards, Richard Broersma Jr. Visit the Los Angles PostgreSQL Users Group (LAPUG) http://pugs.postgresql.org/lapug -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make change

Re: [GENERAL] 0xc3 error Text Search Windows French

2008-06-25 Thread Alvaro Herrera
Andrew wrote: > I have a feeling that an issue I'm running into is related to this: > http://archives.postgresql.org/pgsql-bugs/2008-06/msg00113.php > > On Windows XP running PgAdmin III 1.8.4 against either PostgreSQL 8.3.0 > or 8.3.3 DB, when attempting to do a: > > select * from ts_debug('fr

[GENERAL] POSIX Escape

2008-06-25 Thread Howard Cole
Hello All, Apologies if this is a bit off-topic. Any hints as to what character sequences need escaping in Postgres's regular expressions? Let me show you the problem. If I want to find all strings that start with 'postgres' I use the regex select str ~ '^postgres'. However if str contains

Re: [GENERAL] 0xc3 error Text Search Windows French

2008-06-25 Thread Andrew
One additional aspect. I just ran the create text search dictionary command without the stopfile declaration using the OO dictionaries, and it worked fine with the select ts_lexize('public.fr_ispell', 'catalogue'); command executing with no problems. However, after creating an associated cata

Re: [GENERAL] Probably been asked a hundred times before.

2008-06-25 Thread Chris Browne
[EMAIL PROTECTED] (David Siebert) writes: > Well I am kind of stuck using OpenSuse. Not a bad distro and is the one > we use in our office for production work. > I like CentOS myself for database work and tend to use that for test > systems here since I manage them myself. > I was more wondering if

Re: [GENERAL] 0xc3 error Text Search Windows French

2008-06-25 Thread Andrew
Sorry one last detail. All of my databases are in utf-8 format. My Windows XP is en_AU and defaults to ISO-8859-1 character sets. My postgresql.conf is set to the default for the client_encoding setting, which should then default to the database utf-8 format. Andrew wrote: One additional a

[GENERAL] 0xc3 error Text Search Windows French

2008-06-25 Thread Andrew
I have a feeling that an issue I'm running into is related to this: http://archives.postgresql.org/pgsql-bugs/2008-06/msg00113.php On Windows XP running PgAdmin III 1.8.4 against either PostgreSQL 8.3.0 or 8.3.3 DB, when attempting to do a: select * from ts_debug('french', 'catalogue'); gett

Re: [GENERAL] what are rules for?

2008-06-25 Thread Michael Shulman
On Tue, Jun 24, 2008 at 11:08 AM, Tom Lane <[EMAIL PROTECTED]> wrote: > To expand on that: it's pretty hard to see how update or delete triggers > on a view would work. Insert is easy, because if left to its own > devices the system would in fact try to insert a tuple into the view > relation, and

Re: [GENERAL] Probably been asked a hundred times before.

2008-06-25 Thread David Siebert
Well I am kind of stuck using OpenSuse. Not a bad distro and is the one we use in our office for production work. I like CentOS myself for database work and tend to use that for test systems here since I manage them myself. I was more wondering if someone had made a Postgres centric distro yet. So

[GENERAL] Serialized Access

2008-06-25 Thread Phillip Mills
I'm working on an application that uses EJB3 entities in JBoss, with Hibernate and a PostgreSQL database. One of the entity tables needs consistent, synchronized updates to rows in an environment where telling the user that their operation failed and starting over is not an option. Because it's t

[GENERAL] ERROR: could not open relation with OID 2836

2008-06-25 Thread Rodrigo Gonzalez
PgSQL is returning that error when I open pgdmin and when I run some queries related to pg_buffercache. Also pg_dump cannot dump the DB. PgSQL version is 8.3.3 and happened one day after loading the DB there. Anything that can be done? or I have to restore a backup and put current data again? Th

Re: [GENERAL] Probably been asked a hundred times before.

2008-06-25 Thread Greg Smith
On Tue, 24 Jun 2008, David Siebert wrote: Which disto is best for running a Postgres server? You didn't define what best means for you. If you want to always want to stay current with new releases, the RedHat/Fedora packages available at http://www.postgresql.org/download are on average the

[GENERAL] a question about data corruption

2008-06-25 Thread Jacek Rembisz
Hello, My customer has experienced a serious data corruption. He was using a posgresql version 8.0.3 I know that it is an old version. Postgresql started to log "could not access status of transaction" messages. Since the transaction IDs were far away from what server was using I took a look at

Re: [GENERAL] [BUGS] Reg : Data base deletion

2008-06-25 Thread Bill Moran
In response to "Pradeepa" <[EMAIL PROTECTED]>: > > Could you please explain the scenario in detail. Not sure I understand what you mean ... the scenario is yours to explain. Here is the documentation on configuring PG logging, if that's what you mean: http://www.postgresql.org/docs/8.3/static/ru

Re: [GENERAL] replication

2008-06-25 Thread Andrew Sullivan
On Wed, Jun 25, 2008 at 01:52:00PM +0200, Allan Kamau wrote: > Initially you may want to get the full dump (this applies also to the > replication option) across to your other site. Most of the replication systems I've seen require that _they_ send the data to the remote site, so copying the dat

Re: [GENERAL] pg_dump estimation

2008-06-25 Thread Bill Moran
In response to Allan Kamau <[EMAIL PROTECTED]>: > Sam Mason wrote: > > On Tue, Jun 24, 2008 at 11:13:14PM -0500, Marcelo Martins wrote: > > > >> is there a way to find out / calculate / estimate how big a pg_dump > >> using plain text format for a DB will be ? > >> > > > > How about simp

Re: [GENERAL] pg_dump estimation

2008-06-25 Thread Allan Kamau
Sam Mason wrote: On Tue, Jun 24, 2008 at 11:13:14PM -0500, Marcelo Martins wrote: is there a way to find out / calculate / estimate how big a pg_dump using plain text format for a DB will be ? How about simply doing: pg_dump | wc -c Sam Hi Marcelo, If (using Sam's suggest

Re: [GENERAL] replication

2008-06-25 Thread Allan Kamau
Initially you may want to get the full dump (this applies also to the replication option) across to your other site. You may want to bzip2 the dump file, you may be surprised by the reduction of file size using bzip2. Try "tar -cjf mydump.sql.tar.bz2 mydump.sql" then transfer it using scp or pl

Re: [GENERAL] what are rules for?

2008-06-25 Thread Dean Rasheed
Tom Lane wrote: > To expand on that: it's pretty hard to see how update or delete triggers > on a view would work. Insert is easy, because if left to its own > devices the system would in fact try to insert a tuple into the view > relation, and that action could fire a trigger which could redirec

Re: [GENERAL] [XP SP2/SP3] FATAL: could not reattach to shared memory

2008-06-25 Thread Magnus Hagander
Łukasz Czerpak wrote: > Magnus Hagander wrote: >> >> 487 is "Invalid address". >> >> Do you have any antivirus or similar software on the machine? If so, try >> uninstalling it and trying again (just disabling it is usually not >> enough). >> > > Yes - NOD32. Ok i will check it. NOD32 is known to

Re: [GENERAL] [XP SP2/SP3] FATAL: could not reattach to shared memory

2008-06-25 Thread Łukasz Czerpak
Magnus Hagander wrote: 487 is "Invalid address". Do you have any antivirus or similar software on the machine? If so, try uninstalling it and trying again (just disabling it is usually not enough). Yes - NOD32. Ok i will check it. Is it possible that PostgreSQL works improperly on WinXP + NO

Re: [GENERAL] Probably been asked a hundred times before.

2008-06-25 Thread Tomasz Ostrowski
On 2008-06-24 16:30, David Siebert wrote: > Which disto is best for running a Postgres server? I'd go for CentOS 5.2 (or better RedHat Enterprise Linux 5.2, if you can afford it, as $349/year for basic support can save you several hours of problem solving). But by default CentOS5/RHEL5 have Postg

Re: [GENERAL] LIKE not using indexes (due to locale issue?)

2008-06-25 Thread Klint Gore
Ow Mun Heng wrote: Could it be that it's not able to determine the B2.%.SX in there? explain select count(*) from d_trr_iw where ast_revision like 'B2.P.SX' even this will result in a seq_scan. How many values have you got that start with 'B2.'? If it's more than about 5% then it's probabl

Re: [GENERAL] pg_dump estimation

2008-06-25 Thread Sam Mason
On Tue, Jun 24, 2008 at 11:13:14PM -0500, Marcelo Martins wrote: > is there a way to find out / calculate / estimate how big a pg_dump > using plain text format for a DB will be ? How about simply doing: pg_dump | wc -c Sam -- Sent via pgsql-general mailing list (pgsql-general@postgresq

Re: [GENERAL] [XP SP2/SP3] FATAL: could not reattach to shared memory

2008-06-25 Thread Magnus Hagander
Łukasz Czerpak wrote: > Hi, > > We have problems with PostgreSQL on Windows. > > PostgreSQL: 8.3.1 > System: Windows XP (SP3) > FS: NTFS > Hardware: IBM x3650, 1x Xeon Quad, 2GB RAM > > > The database is accessed from multiple windows apps. One of them has a > connection pool, the others use si

Re: [GENERAL] LIKE not using indexes (due to locale issue?)

2008-06-25 Thread Ow Mun Heng
On Wed, 2008-06-25 at 17:00 +1000, Klint Gore wrote: > Ow Mun Heng wrote: > > On Wed, 2008-06-25 at 14:58 +1000, Klint Gore wrote: > > > Ow Mun Heng wrote: > > > > explain select * from d_trr where revision like '^B2.%.SX' > > > > --where ast_revision = 'B2.M.SX' > > > > > > > > Seq Scan on d_trr

[GENERAL] [XP SP2/SP3] FATAL: could not reattach to shared memory

2008-06-25 Thread Łukasz Czerpak
Hi, We have problems with PostgreSQL on Windows. PostgreSQL: 8.3.1 System: Windows XP (SP3) FS: NTFS Hardware: IBM x3650, 1x Xeon Quad, 2GB RAM The database is accessed from multiple windows apps. One of them has a connection pool, the others use single connection per app. Somethimes when I st

Re: [GENERAL] LIKE not using indexes (due to locale issue?)

2008-06-25 Thread Klint Gore
Ow Mun Heng wrote: On Wed, 2008-06-25 at 14:58 +1000, Klint Gore wrote: > Ow Mun Heng wrote: > > explain select * from d_trr where revision like '^B2.%.SX' > > --where ast_revision = 'B2.M.SX' > > > > Seq Scan on d_trr (cost=0.00..2268460.98 rows=1 width=16) > > Filter: ((revision)::text ~~ '