"Stephane Charette" <[EMAIL PROTECTED]> writes:
> The error received when we run "vacuumdb" is:
> -> ERROR: Cannot insert a duplicate key into unique index
> pg_class_oid_index
That's pretty interesting. My first thought is a corrupt index.
Please try reindexing pg_class. You'll need to do thi
>> Now I've made a change and I find myself using the command "vacuumdb
>> -f foo" to perform a full vacuum. However, I've noticed that vacuum
>> full seems to return non-zero return values much more often.
>
>This is not a very useful statement. What would be useful is to see the
>error messages
ferdinan firmansyah wrote:
We have installed LinuxRedhat+PgSQL in our server. We
can ping the server's IP. But we cannot connect our
database through PGAdmin or our application. We have
already set the port to the default.
1. What seems to be the problem?
Check to see if you installed RedHat w
Oops...
> Nope, this is definitely a message from the postgresql backend.
What I *meant* to type was:
this is definitely a message from the postgresql backend referring to too
many client connections.
---(end of broadcast)---
TIP 2: you can get o
>> If you aren't using pooled
>> connections, maybe you just have more users on the web.
>
> But is there really that number of backends/connections present?
Assuming there is no connection pooling going on, then yes, it is reasonable
to assume that more users means more connections. (I don't kn
AM-
The band-aid patch is to increase the number of connections available. Check
out this link to the idocs:
http://www.postgresql.org/idocs/index.php?runtime-config.html
Maybe that will keep things running for you while you go over the code to
learn why you're using more connections now. If you
OMG, I'm about to rip my hair out. I've been writing a webapp using
DBD::Pg and it has been accessing postgresql for weeks without
problems. Suddenly this morning with no changes to the setup, I get:
FATAL 1: Sorry, too many clients already
whenever I try to use the webapp (running under user "a
On Mon, Nov 04, 2002 at 02:49:32PM -0600, Adam Erickson wrote:
> Has anyone used postgres w/ an external disk array? I'm sure a single
> postgres instance would work fine with one.
Yes.
> While researching the server clustering techniques of other RDBMS I
> came upon Oracle 9's "RAC" clustering.
Hi all.
Becuse of an HD failure, all my databases went away. I recovered them from
a backup, but some customers need a more up to date version (the backup is
one week old).
I recovered all files in data/base/* , but I wasn't able to start postgres
using those files within a clean installation.
I
Our client is running a large-ish database, and has infrequently been
getting the following messages:
Nov 6 04:17:09 dolidb-n1 logger: NOTICE: Rel pg_type: Uninitialized
page 6 - fixing
Nov 6 04:17:09 dolidb-n1 logger: NOTICE: Rel pg_type: Uninitialized
page 7 - fixing
Nov 6 04:17:09 dolidb-n
On 4 Nov 2002 at 17:26, ferdinan firmansyah wrote:
> We have installed LinuxRedhat+PgSQL in our server. We
> can ping the server's IP. But we cannot connect our
> database through PGAdmin or our application. We have
> already set the port to the default.
>
> 1. What seems to be the problem?
> 2.
On Mon, 4 Nov 2002, ferdinan firmansyah wrote:
> We have installed LinuxRedhat+PgSQL in our server. We
> can ping the server's IP. But we cannot connect our
> database through PGAdmin or our application. We have
> already set the port to the default.
>
> 1. What seems to be the problem?
Find you
Hi Folks,
DBMirror had been working very fine till recently. but is facing a problem
currently.
certain "Data" column in the "PendingData" Table which DBMirror.pl script uses
has the stuff below:
"company_id"='78111' "comp_name"='SUBAIDA JEWELLERY' "office_addr"='NEW.43, NSC BOSE
ROAD, ' "ph
13 matches
Mail list logo
