I have found and deleted an entry with pg_class.relnamespace=559701082
but nowhere else. I still cannot dump the schema. Is there something
like a system catalog integrity checker?
The problem I'm facing is the following:
cs1=# select relname from pg_class where relname like 'bm%';
On Tue, Nov 29, 2005 at 01:21:12 +0100,
Diego Cattelan <[EMAIL PROTECTED]> wrote:
>
> >What exact commands are you using for both the backup and the restore?
> >
> - at boot time the linux box mount a smb share '/mnt/walarchive810'
> - I have modified postgresql.conf parameter
> archive_co
=?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= <[EMAIL PROTECTED]> writes:
> Yes, I think so. What search path do you mean? These tables were all
> temporary tables.
In that case they're most likely *not* in your search path, unless your
session happens to have seized on the same pg_temp_nn schema they are
in
Yes, I think so. What search path do you mean? These tables were all
temporary tables.
Dirk
Tom Lane wrote:
=?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= <[EMAIL PROTECTED]> writes:
The problem I'm facing is the following:
cs1=# select relname from pg_class where relname like 'bm%';
r
=?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= <[EMAIL PROTECTED]> writes:
> The problem I'm facing is the following:
> cs1=# select relname from pg_class where relname like 'bm%';
>relname
> ---
> bm_pagehits_1133271374_047421_941
> bm_pagehits_1133271378_92
Ahh, ok. There's a couple issues here. Both the data files and WAL logs
are in a binary format that is not necessarily compatable across
different OSes. I don't know if linux to windows should work by design
or not, but it wouldn't surprise me if it won't work.
Another issue is hardware. One examp
Bruce Momjian writes:
> Should we start planning for an 8.1.1?
Yeah, it's getting to be that time.
regards, tom lane
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choos
Tom Lane wrote:
> Kari Lavikka <[EMAIL PROTECTED]> writes:
> > Some backtraces (update queries are included in the bt):
> >http://tuner.bdb.fi/pg_crashing.txt
> >http://tuner.bdb.fi/pg_crashing2.txt
> >http://tuner.bdb.fi/pg_crashing3.txt
>
> This looks to be the toast-vs-index bug alr
Kari Lavikka <[EMAIL PROTECTED]> writes:
> Some backtraces (update queries are included in the bt):
>http://tuner.bdb.fi/pg_crashing.txt
>http://tuner.bdb.fi/pg_crashing2.txt
>http://tuner.bdb.fi/pg_crashing3.txt
This looks to be the toast-vs-index bug already identified.
Patch is here
Hi!
I just upgraded pg 8.0.3 to 8.1 (dump and reload) and outcome was a
corrupted database. pg 8.1 seemed to fly but backends were crashing
:-/
Hardware is Sun v40z with 64bit Debian Sarge, Linux 2.6.13.2. Size of
database is somewhere around 500M rows and it's loaded by a website with a
lo
my previous post just vanished...
Hi!
I just upgraded pg 8.0.3 to 8.1 (dump and reload) and outcome was a
corrupted database. pg 8.1 seemed to fly but backends were crashing :-/
While tailing the log file I noticed a couple of:
ERROR: invalid memory alloc request size 1101389186
Hardware
=?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= <[EMAIL PROTECTED]> writes:
> I get the following error when I call:
> # pg_dump db
> pg_dump: schema with OID 559701082 does not exist
I suspect a corrupted catalog entry. Look through your system catalogs
for an entry referring to namespace 559701082 --- you w
"Arjen" <[EMAIL PROTECTED]> writes:
>-> BitmapAnd (cost=5.62..5.62 rows=1 width=0)
> -> Bitmap Index Scan on pwprodukten_cat2_popuindex
> (cost=0.00..2.50 rows=144 width=0)
>Index Cond: (cat2 = 51)
> -> Bitmap Index Scan on pwprodukten_cat2_zichtbaar
> (c
Hi,
I get the following error when I call:
# pg_dump db
pg_dump: schema with OID 559701082 does not exist
this happens with 8.0.1 on RHEL 3.0. I cannot dump the database neither
with --schema-only or --data-only.
What can I do?
Thanks for help,
Dirk
---(end of bro
Aaron Dummer wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2073
> Logged by: Aaron Dummer
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.3
> Operating system: Debian Linux
> Description:Can't drop sequence when created via SERIA
On Mon, Nov 28, 2005 at 05:49:02PM +0100, Stefano Reksten wrote:
> Should not a char(10) insert 6 padding spaces? Or am I missing something
> like an update in the SQL standard?
Use char_length(string).
regards
--
Paweł Bernat; uselessness' lover;
select''as email;
Slowly and surely the unix cre
The following bug has been logged online:
Bug reference: 2073
Logged by: Aaron Dummer
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Debian Linux
Description:Can't drop sequence when created via SERIAL column
Details:
If I create a tabl
The following bug has been logged online:
Bug reference: 2075
Logged by: Arjen
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0
Operating system: Gentoo linux (2.6.11 kernel)
Description:Strange choice of bitmap-index-scan
Details:
I haven't tried a minima
The following bug has been logged online:
Bug reference: 2076
Logged by: Farid Z
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Windows 2000
Description:8.01.01.00 driver transaction error
Details:
ERROR: current transaction is aborted, c
The following bug has been logged online:
Bug reference: 2074
Logged by: Edoardo Innocenti
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0
Operating system: Linux
Description:Error switching connection in embedded PostgreSQL
program
Details:
We have probl
20 matches
Mail list logo
