The following bug has been logged on the website:
Bug reference: 7511
Logged by: Adrian Dries
Email address: i...@avdd.co
PostgreSQL version: Unsupported/Unknown
Operating system: any
Description:
In trying 9.2 I find pg_stat_activity.procpid has been renamed to pid.
i...@avdd.co writes:
> In trying 9.2 I find pg_stat_activity.procpid has been renamed to pid.
Yup. Sorry, that change is not going to get undone at this point.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your sub
On Thu, Aug 30, 2012 at 04:34:18AM +, i...@avdd.co wrote:
> The following bug has been logged on the website:
>
> Bug reference: 7511
> Logged by: Adrian Dries
> Email address: i...@avdd.co
> PostgreSQL version: Unsupported/Unknown
> Operating system: any
> Description:
this is the stack trace
thx in advance :D
$ ps aux | grep 4500
postgres 4500 4.2 14.0 14134172 13924240 ? Ds Aug29 60:44 postgres:
startup process recovering 000240A300B4
$ gstack 4500
#0 0x0037d10c63a0 in __read_nocancel () from /lib64/libc.so.6
#1 0x005dc88a i
it is still stuck on the same wal record ->
now | pg_last_xlog_replay_location
---+--
2012-08-30 14:57:57.617171+00 | 40A3/B4D62038
and iostat shows 100% util on one disk ->
sdj 90.60 0.00 176.0
We have successfully upgraded Postgresql from 8.4.3 to 9.1.4 in our
environment, but we have some questions/issues.
Before the upgrade:
Postgres8 data location -- /usr/local/pgsql/data -->
/u01/fiber/postgres843/postgres_data
Postgres9 data location -- /opt/PostgreSQL/9.1/data -->
/u01/fiber/post
On Thu, Aug 30, 2012 at 02:48:51PM -0400, Freddie Burgess wrote:
> We have successfully upgraded Postgresql from 8.4.3 to 9.1.4 in our
> environment, but we have some questions/issues.
>
> Before the upgrade:
> Postgres8 data location -- /usr/local/pgsql/data -->
> /u01/fiber/postgres843/postgres
I have looked at darn near every listing for this bug ..
"..because curl is loaded before postgresql" << nope didn't work
here is my system specs
CentOS 5.8 64bit
24gb ram
dual i7
php 5.3.16
let yum install 8.1.4 got the error either in a php script or command line
deleted 8.1.4, rpm'd 9.1.5
On 30 August 2012 20:29, Jeff Lake wrote:
> I have looked at darn near every listing for this bug ..
> "..because curl is loaded before postgresql" << nope didn't work
> here is my system specs
This must be the worst bug report I've ever seen. I'd give the usual
link to "How to Report Bugs Effec
Lack even basic manners??
I have been at installing this for 3 days
manners/patience is gone!!
lets see MySql works , Oracle works...
install PostgreSQL
nope it don't work, either using Command line, php, for the hell of I
tried perl
nope all fail, all segmentation fault so what would that say
On Fri, Jun 22, 2012 at 10:37:10PM -0400, Tom Lane wrote:
> j...@pgexperts.com writes:
> > DROP and CREATE extension appear to work fine, but if you ALTER EXTENSION
> > postgis SET SCHEMA foo, it leaves a few relations behind.
>
> What it seems to be leaving behind is indexes ... also relation row
On Mon, Jul 2, 2012 at 04:16:31PM +0530, Amit Kapila wrote:
> > From: pgsql-bugs-ow...@postgresql.org
> > [mailto:pgsql-bugs-ow...@postgresql.org] On Behalf Of
> > miroslav.s...@fordfrog.com
> > Sent: Saturday, June 30, 2012 4:28 PM
> > The following bug has been logged on the website:
>
> > Bu
On 30 August 2012 22:42, Jeff Lake wrote:
> Lack even basic manners??
> I have been at installing this for 3 days
> manners/patience is gone!!
That's not my problem. Projecting your frustration on this mailing
list isn't cool, and, along with your poor description of the problem,
is a sure way to
Bruce Momjian writes:
> On Fri, Jun 22, 2012 at 10:37:10PM -0400, Tom Lane wrote:
>> j...@pgexperts.com writes:
>>> DROP and CREATE extension appear to work fine, but if you ALTER EXTENSION
>>> postgis SET SCHEMA foo, it leaves a few relations behind.
>> What it seems to be leaving behind is inde
Excerpts from Tom Lane's message of jue ago 30 23:19:12 -0400 2012:
> Bruce Momjian writes:
> > On Fri, Jun 22, 2012 at 10:37:10PM -0400, Tom Lane wrote:
> >> j...@pgexperts.com writes:
> >>> DROP and CREATE extension appear to work fine, but if you ALTER EXTENSION
> >>> postgis SET SCHEMA foo, it
15 matches
Mail list logo
