"Chad R. Larson" <[EMAIL PROTECTED]> writes:
> At 08:25 AM 8/13/02 , Robert M. Meyer wrote:
>> I had the same problem. I rewrote my shutdown script to call 'pg_ctl -m
>> immediate'. So far, I haven't seen any damage because of it and we always
>> restart tomcat at some point in the middle of th
I said:
> Oh, duh! You don't need to be using NOTIFY explicitly --- you just have
> to sit idle long enough to make the SI buffer overflow, and the system
> will try to NOTIFY your backend anyway to make it read the SI message
> buffer. Which is the path I was looking at --- that will leave
> Imm
"Ed L." <[EMAIL PROTECTED]> writes:
> On Monday February 17 2003 5:09, Tom Lane wrote:
>> Hm, I suddenly have a theory. Do you guys use LISTEN/NOTIFY in the
>> databases that are exhibiting the problem?
> Not using LISTEN/NOTIFY here, at least not of which I'm aware. I'll
> dig a little more an
Did this ever get addressed?
---
Tom Lane wrote:
> Ian Burrell <[EMAIL PROTECTED]> writes:
> > I just recreated the problem with a slightly different command. The
> > problem was caused by using a list file to skip loading
On Monday February 17 2003 4:31, Mona Gamboa wrote:
> ok...here's the output.[kinda nasty to read]
Nothing obvious to me. If it is reproduceable, you might try turning
on some of the lock tracing directives in postgresql.conf and/or
increasing the logging level. You might also try attaching to
"Ed L." <[EMAIL PROTECTED]> writes:
> I've been seeing the same problem intermittently over the past 2 years
> among ~30 production clusters.
Hm, I suddenly have a theory. Do you guys use LISTEN/NOTIFY in the
databases that are exhibiting the problem? Is it possible that the
backends that aren'
Laurette Cisneros <[EMAIL PROTECTED]> writes:
> Ok, my production server had this problem (again). So, here's the info.
> you requested. There's a lot of postgres processes still left running:
> postmaster (proc id 1457):
> (gdb) print Shutdown
> $1 = 2
Okay, so the postmaster definitely got th
ok...here's the output.[kinda nasty to read]
uname -a
Linux aus-db-1.loopone.com 2.4.9-e.3enterprise #1 SMP Fri May 3
16:35:33 EDT 2002 i686 unknown
[postgres@aus-db-1 postgres]$ grep ^log_ $PGDATA/postgresql.conf
log_connections = true#changed this whole block to true -- by
Mona G. log_pid
Ok, my production server had this problem (again). So, here's the info.
you requested. There's a lot of postgres processes still left running:
postmaster (proc id 1457):
(gdb) print Shutdown
$1 = 2
Other backends (postgres) still hanging around:
postgres 1458 1457 0 Feb06 ?00:22:41 p
we are running linux and postgres7.3.2 in a
production environment.
the database just 'locks ups.' if i try to
get into psql X [where X is my database or template 0 or template 1] it
just sits there.
the log files don't say anything..there's
no indication as to what is happening.
In my opinion there are no usefull solutions for
this unless you always use single column indexing.
For example:
SELECT * FROM mytable WHERE lower(mycolumn) <=
'mycondition' ORDER BY lower(mycolumn);
will give case insensitive ordering and if you want
it to use an index for perfomance then yo
On Monday 17 February 2003 19:56, Tom Lane wrote:
> Andreas Schmitz <[EMAIL PROTECTED]> writes:
> > I think it is not the same. When I ran the vaccum when no other clients
> > whe= re=20
> > connected to the database.
>
> The vacuum that reports the NOTICEs is not the one that created the
> problem
You really need to upgrade to 7.2.3/7.2.4. This issue is fixed in 7.2.3.
To fix this problem, stop postmaster, make a dummy clog containing zeros
(/dev/zero), start postmaster. for security you can dump all data then
(perhaps you need to repeat the clog dummy step) and freshly re-insert it.
Regar
That is going to use the identd server on your machine, not NIS.
---
Yung-Min Chen wrote:
> Can anybody tell me how to set up pgsql authentication using NIS password database?
>
> I set my pg_hba.conf as following:
>
> hos
Martins Zarins <[EMAIL PROTECTED]> writes:
> FATAL 2: open of /usr/local/pgsql/data/pg_clog/0943 failed: No such file or
> directory
You evidently have a row with a corrupted transaction number in that
table. The system is trying to look up the status of that transaction,
and it's failing becau
Sorry, we will have point-in-time recovery in 7.4. Right now, the only
solution is a async replication using something like /contrib/dbmirror
or /contrib/rserv.
---
Mel Jamero wrote:
> Hi!
>
> What's the best way to make i
I have this error in postgres log
FATAL 2: open of /usr/local/pgsql/data/pg_clog/0943 failed: No such file or
directory
When it happend i did indexing on big table (~32M rows)
On small selects, inserts, updates all seems to work fine, but when I try to
do select count(*) from big table or intex
Andreas Schmitz <[EMAIL PROTECTED]> writes:
> I think it is not the same. When I ran the vaccum when no other clients whe=
> re=20
> connected to the database.
The vacuum that reports the NOTICEs is not the one that created the
problem. The scenario I was talking about requires concurrent clients
Do you perhaps have an old version of jdbc on that machine?
---
Randolph Jones wrote:
> I have pg 7.3.2 running on rh8 2.4.19.
> I have pg_hba.conf with line
> host testt user xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx md5
>
> I can l
> The last lines of output were:
>
>
> NOTICE: Rel pg_class: Uninitialized page 3344 - fixing
>
[...]
> NOTICE: Rel pg_class: Uninitialized page 3355 - fixing
>
> NOTICE: Rel pg_class: Uninitialized page 3356 - fixing
>
> batch/nachts.sh: line 3: 30855 Segmentation fault /usr/bin/php -q
>
On Thu, 13 Feb 2003, mlw wrote:
> You will not be able to get that many connections on a cygwin version of
> PostgreSQL. I think cygwin's limit is something like 64.
>
> P G wrote:
>
> >I need to increase the default max connection setting
> >from 32 to over 500. What other parameters should I
I have pg 7.3.2 running on rh8 2.4.19.
I have pg_hba.conf with line
host testt user xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx md5
I can log on as user thru psql -h xxx.xxx.xxx.xxx testt
pgsql asks for password, allows logon to testt
I have a java program using user password that gets
authentication failed fo
Which is the diference between that system tables?
Which is their objetive?
Thanks.
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
I've had PostgreSQL 7.1.3 running (Mac OS X) for a while. I recently
upgraded to MAC OS X 10.2 (and it appeared that my 7.1.3 install of
PostgreSQL no longer works). So I've been trying to upgrade to 7.3.
The installation package ran fine. However, when I ran the initdb
command, it failed.
Can anybody tell me how to set up pgsql authentication using NIS password database?
I set my pg_hba.conf as following:
hostall10.0.1.0255.255.255.0identsameuser
But I'm still getting "user does not exist" error. Any suggestion will be very much
appreciated.
Thanks in advanc
Hi!
What's the best way to make incremental back-ups?
Is there a tool (GUI or otherwise, open source perhaps) for this?
Red Hat Linux 7.2. PostgreSQL 7.1
thanks,
Mel
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unr
Hello All,
I have installed postgresql on windows NT 4.0.But it is giving this problem when i am giving this command.
The programs 'postmaster' and 'psql' are needed by pg_ctl butwere not found in the directory '/usr/bin'.Check your installation.
I checked the installation in the default p
I have already tried to spread my databases to different hd as Oliver
Elphick sugestion and it works ( thx so much Olly )
But I don't have experiences for spreading schemas as you told. Maybe the
other masters of postgreSQL want to explain about that.
Best Regards
Aris Wendy
On Tuesday 11
28 matches
Mail list logo
