On Fri, 6 Mar 2009 16:25:56 -0600 (CST)
Richard Ray wrote:
> That was the problem
> Priorities were killing me
No problem!
Glad to be able to return the favors to community.
--
|Jakov Sosic|ICQ: 28410271| PGP: 0x965CAE2D |
==
On Fri, 6 Mar 2009, Jakov Sosic wrote:
On Fri, 6 Mar 2009 15:59:08 -0600 (CST)
Richard Ray wrote:
Maybe priorities are broken? Maybe some other repo than pgdg3 has
higher priority for postgresql, and yum then won't upgrade postgresql
because it already has newer version than for example b
On Fri, Mar 6, 2009 at 2:59 PM, Richard Ray wrote:
> Excluding Packages in global exclude list
> Finished
So, postgresql is for sure NOT in your exclude list(s)?
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mai
On Fri, 6 Mar 2009 15:59:08 -0600 (CST)
Richard Ray wrote:
Maybe priorities are broken? Maybe some other repo than pgdg3 has
higher priority for postgresql, and yum then won't upgrade postgresql
because it already has newer version than for example base/updates?
try leaving only pgdg83.repo in
On Fri, 6 Mar 2009, Jakov Sosic wrote:
On Fri, 6 Mar 2009 09:16:04 -0600 (CST)
Richard Ray wrote:
# yum update postgresql
Have you tried:
# yum update postgresql*
# yum update postgresql*
Loading "fastestmirror" plugin
Loading mirror speeds from cached hostfile
* pgdg83: yum.pgsqlrpms.o
On Fri, 6 Mar 2009 09:16:04 -0600 (CST)
Richard Ray wrote:
> # yum update postgresql
Have you tried:
# yum update postgresql*
Also, if that doesn't work, try this:
# yum update
and see the list of packages ready to be upgraded.
And if even that doesn't work, do the following:
# yum clean a
On Wed, Mar 04, 2009 at 03:14:51PM -0500, Ray Stell wrote:
> On Wed, Mar 04, 2009 at 03:06:12PM -0500, Ray Stell wrote:
> > Testing pg_standby in 8.3.6. I've gotten this standby into some sort of
> > bind. It seems like it may be waiting for some WAL. How can I tell
> > what it is waiting on?
On Mar 6, 2009, at 11:10 AM, Tom Lane wrote:
Carol Walter writes:
Well, it seems like that could happen. This is a machine that has a
instance of 8.2 running on it. My bash history says that the command
that I ran to start the 8.3.6 instance is
pg_ctl start -D /db02/postgres/data8.3.6/data
Carol Walter writes:
> Well, it seems like that could happen. This is a machine that has a
> instance of 8.2 running on it. My bash history says that the command
> that I ran to start the 8.3.6 instance is
> pg_ctl start -D /db02/postgres/data8.3.6/data -l data836.log. /db02/
> postgres/da
On Mar 6, 2009, at 10:37 AM, Tom Lane wrote:
Carol Walter writes:
I am building a test instance of PosgreSQL 8.3.6 on a Solaris 10 box.
When start the server, if fails to start. In the log there are these
statements...
-bash-3.00$ more data836.log
FATAL: unrecognized configuration parame
Carol Walter writes:
> I am building a test instance of PosgreSQL 8.3.6 on a Solaris 10 box.
> When start the server, if fails to start. In the log there are these
> statements...
> -bash-3.00$ more data836.log
> FATAL: unrecognized configuration parameter
> "default_text_search_config"
> I'm curious why you are focused on the archive on the primary?
Postgres docs do not say that during initial recovery you need a backup
history file. But It is required during initial recovery. That's why I am
focused on it.
You lost 0002001C.00512178.backup. That means your ar
Hello,
I am building a test instance of PosgreSQL 8.3.6 on a Solaris 10 box.
When start the server, if fails to start. In the log there are these
statements...
-bash-3.00$ more data836.log
FATAL: unrecognized configuration parameter
"default_text_search_config"
FATAL: unrecognized con
I have installed pgdg-centos-8.3-5.noarch.rpm
Using that repo I installed
compat-postgresql-libs-4-1PGDG.rhel5
postgresql-server-8.3.5-2PGDG.rhel5
postgresql-contrib-8.3.5-2PGDG.rhel5
postgresql-docs-8.3.5-2PGDG.rhel5
postgresql-libs-8.3.5-2PGDG.rhel5
postgresql-8.3.5-2PGDG.rhel5
postgresql-pltcl-
hello,everyone.
I have a c test-program for "select query",if the program create
thread every 3ms,it runs smoothly.but when the duration time interval reduce
to 2.8ms,the sleeping process increase more and more,and then the server
crash.the cpu and memory used percentage under 50%.
15 matches
Mail list logo