On Tue, Jul 17, 2012 at 12:01 AM, Trey Chadick wrote:
> Excerpts from Dave Page's message of mar jun 05 14:38:54 -0400 2012:
>>
>> On Sun, May 20, 2012 at 7:05 PM, Alvaro Herrera
>> wrote:
>
>> >> I have been installing PostgreSQL 9.1.3.2, and I've noted that 'creating
>> >> database cluster' is
> From: Noah Misch [n...@leadboat.com]
> Sent: Monday, July 16, 2012 8:42 PM
> On Mon, Jul 16, 2012 at 04:49:46PM +0530, Amit Kapila wrote:
>> > Care to prepare a patch with a test case addition?
>> Let me know if above is sufficient or shall I include anything more in
>> patch.
> I can't think
On 13 July 2012 14:38, wrote:
> 2012-07-13 17:06:19.732 MSK 79724 @ from [vxid:1/0 txid:0] []PANIC: WAL
> contains references to invalid pages
The problem is not connected with Hot Standby. The issue relates to
index code that contains problems, leaving invalid pages. These are
not reported u
The following bug has been logged on the website:
Bug reference: 6740
Logged by: sobhit
Email address: sobhit.pande...@gmail.com
PostgreSQL version: 9.0.8
Operating system: windows
Description:
I am using postgreSQL 9.0.8 for an Indian company and have a small problem
>From: pgsql-bugs-ow...@postgresql.org [mailto:pgsql-bugs-ow...@postgresql.org]
>On
> Behalf Of sobhit.pande...@gmail.com
> The following bug has been logged on the website:
> Bug reference: 6740
> Logged by: sobhit
> Email address: sobhit.pande...@gmail.com
> PostgreSQL vers
The following bug has been logged on the website:
Bug reference: 6741
Logged by: Peter
Email address: ry...@hotmail.com
PostgreSQL version: 9.1.3
Operating system: Linux
Description:
i have been getting the message below in the logs whats causes these
statements t
ry...@hotmail.com writes:
> i have been getting the message below in the logs whats causes these
> statements to appear in the logs?
> process 11812 acquired ExclusiveLock on extension of relation 60777 of
> database 16387 after 1392.303 ms
> LOG: process 24079 still waiting for ExclusiveL
Hello Tom and all,
Thank you for following up on this.
1. log_timezone:
admin_datamart=# show log_timezone;
log_timezone
--
US/Pacific
(1 row)
I have been playing around with changing log_rotation_age = 7h, +/- 1 hour
to see if I can get the elapse timing right. The shutdown/star
On Sun, Jul 15, 2012 at 02:15:35PM -0700, Mike Wilson wrote:
> I've had some time to examine this closer over the weekend. It appears that
> pg_upgrade for 9.2b2 segfaults which more than likely has something to do with
> the resulting converted database appearing to have no rows. Earlier in this
On Tue, Jul 17, 2012 at 04:01:08PM -0700, Mike Wilson wrote:
> Please find below the full pg_upgrade output. Let me know if there are any
> other questions that I may have missed. Note, the attached pg_upgrade stdout
> log is for the schema only pg_dumpall upgrade attempt from PG842 -> PG920b2.
Given the stack trace previously supplied and that the pg_upgrade from 9.1.4
does actually complete successfully can you recommend how I might continue to
diagnose the issue myself? Since the 9.1.4 version of pg_upgrade did work I've
started to look at the source for pg_upgrade in an attempt to
On Tue, Jul 17, 2012 at 05:41:05PM -0700, Mike Wilson wrote:
> Given the stack trace previously supplied and that the pg_upgrade from 9.1.4
> does actually complete successfully can you recommend how I might continue to
> diagnose the issue myself? Since the 9.1.4 version of pg_upgrade did work
>
Bruce Momjian writes:
> I am using git head for testing. Tom sees a few things odd in
> load_directory() that might be causing some problems on Solaris, and
> this is new code for 9.2 for Solaris, so that might explain it. I think
> we need Tom to finish and then if you can grab our git source a
13 matches
Mail list logo
