Mike Krüger wrote:
Sorry, I lost the Email Adress of the List.
No problem, just remember to hit "reply all" rather than "reply".
There are no problems with other Processes.
The System is only slow, when the postmaster Prozess gets the 100 % CPU time.
Can I configure it, that this Prozess dont
"Sivaraman K.G" <[EMAIL PROTECTED]> writes:
> \d command used to give the existing relations in the database.
> But now it is saying :
> ERROR : Cache lookup failed for relation 17233.
Not a lot of information to go on here. What do you get from
select * from pg_class where oid = 17233;
Can you
"George Jansen" <[EMAIL PROTECTED]> writes:
> [ inconsistent comparison behavior ]
> Both old and new databases use SQL_ASCII. Is this a bug?
I think it's probably a locale problem; did you initdb the database in C
locale? (Check SHOW LC_COLLATE and SHOW LC_CTYPE to be sure.) Usually
we see this
"Chris Hoover" <[EMAIL PROTECTED]> writes:
> I was working with my pg_hba.conf file and did a pg_ctl -D reload. I
> received the following message, and postgresql shutdown.
> [EMAIL PROTECTED] eedi]$ pg_ctl -D /database/data/eedi/ reload
> postmaster signaled
> [EMAIL PROTECTED] eedi]$ *** glibc
> Bug reference: 1812
> Logged by: Donald Bahari
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.3
> Operating system: Windows XP Home SP2
> Description:installation
> Details:
>
> in the first screen of the installation the user was set to
> postgres an
> Bug reference: 1799
> Logged by: HAUSERMANN Laurent
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.3
> Operating system: Windows 2000
> Description:Auto Creation of Strong Password fails
> Details:
>
> I ran the Postgresql 8.0.3 msi installer on a "pos
> The following bug has been logged online:
>
> Bug reference: 1805
> Logged by: Vahe
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8
> Operating system: windows XP
> Description:FATAL: invalid command-line arguments for
> server process
> HINT: Try "postgr
"CHRIS HOOVER" <[EMAIL PROTECTED]> writes:
>> I was working with my pg_hba.conf file and did a pg_ctl -D reload. I
>> received the following message, and postgresql shutdown.
>> [EMAIL PROTECTED] eedi]$ pg_ctl -D /database/data/eedi/ reload
>> postmaster signaled
>> [EMAIL PROTECTED] eedi]$ ***
The following bug has been logged online:
Bug reference: 1814
Logged by: Ian Burrell
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.6
Operating system: RHEL 3 x86_64
Description:Cancelling a CLUSTER changes the OID counter
Details:
Cancelling a CLUSTER is
I was playing around and had most entries uncommented, even if I did not
change the values. I am attaching the cleaned up postgresql.conf and my
pg_hba.conf files for you.
Chris Hoover
Application Development System Analyst 2
Companion Technologies
8901 Farrow Rd.
Columbia, SC 29203
Phone: (80
"Ian Burrell" <[EMAIL PROTECTED]> writes:
> Cancelling a CLUSTER is causing the OID counter to jump forwards. In the
> test below, it goes from 108 million to 4286 million (close to 2^32).
[ scratches head... ] Cannot duplicate this here. Does anyone else
see it?
regard
"Ian Burrell" <[EMAIL PROTECTED]> writes:
> Cancelling a CLUSTER is causing the OID counter to jump forwards. In the
> test below, it goes from 108 million to 4286 million (close to 2^32).
> We recently wrapped the OID counter.
Uh, does the same thing happen if you *don't* cancel it?
It looks t
12 matches
Mail list logo
