On Tue, Jun 12, 2012 at 05:10:19PM +1200, Edmund Horner wrote:
> On 26 May 2012 01:10, Bruce Momjian wrote:
> > Ah, turns out I only need one extra log file on Windows, not two,
> > because I can reuse the utility file for pg_ctl stop. The original
> > beta1 code usesd the utility file for pg_ctl
On 26 May 2012 01:10, Bruce Momjian wrote:
> Ah, turns out I only need one extra log file on Windows, not two,
> because I can reuse the utility file for pg_ctl stop. The original
> beta1 code usesd the utility file for pg_ctl stop and start, which is
> what caused the problem.
>
> Applied patch
On Thu, May 24, 2012 at 08:34:01PM -0400, Bruce Momjian wrote:
> On Fri, May 25, 2012 at 11:48:53AM +1200, Edmund Horner wrote:
> > It still fails (when run in verbose mode):
> >
> > Creating catalog dump
> > ""c:\ehorner\pgsql\bin/pg_dumpall" --port 50432 --username "ehorner"
> > --schema-onl
On Fri, May 25, 2012 at 11:48:53AM +1200, Edmund Horner wrote:
> It still fails (when run in verbose mode):
>
> Creating catalog dump
> ""c:\ehorner\pgsql\bin/pg_dumpall" --port 50432 --username "ehorner"
> --schema-only --binary-upgrade --verbose > "pg_upgrade_dump_all.sql"
> 2>> "pg_upgrade_
On 25 May 2012 11:48, Edmund Horner wrote:
> It still fails (when run in verbose mode):
Sorry, let me correct that to:
It still fails, regardless of verbose mode. And, in verbose mode, the
output is...
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your sub
On 25 May 2012 01:59, Bruce Momjian wrote:
> On Thu, May 24, 2012 at 03:42:25PM +0200, Magnus Hagander wrote:
>> I've built a new one off git master + Bruce's patch. You can get it
>> from http://www.hagander.net/tmp/pg_upgrade.zip - please see if that
>> one works for you.
>
> Thanks, but thinkin
On Thu, May 24, 2012 at 03:42:25PM +0200, Magnus Hagander wrote:
> On Thu, May 24, 2012 at 2:40 AM, Edmund Horner wrote:
> > On 24 May 2012 12:33, Bruce Momjian wrote:
> >> I have applied the attached patch which should fix the problem. How
> >> can we get Edmund a copy of a new binary for test
On Thu, May 24, 2012 at 2:40 AM, Edmund Horner wrote:
> On 24 May 2012 12:33, Bruce Momjian wrote:
>> I have applied the attached patch which should fix the problem. How
>> can we get Edmund a copy of a new binary for testing? Does he have to
>> wait for beta2?
>
> My uneducated guess is that
On 24 May 2012 12:33, Bruce Momjian wrote:
> I have applied the attached patch which should fix the problem. How
> can we get Edmund a copy of a new binary for testing? Does he have to
> wait for beta2?
My uneducated guess is that your patch will fix the problem.
But I don't think I'm up to c
On Wed, May 23, 2012 at 03:20:30PM +0200, Magnus Hagander wrote:
> On Wed, May 23, 2012 at 5:50 AM, Edmund Horner wrote:
> > On 22 May 2012 18:49, Craig Ringer wrote:
> >> When you shut down the 9.1.3 cluster did you make absolutely certain there
> >> were no postgres.exe processes lurking around
On Wed, May 23, 2012 at 5:50 AM, Edmund Horner wrote:
> On 22 May 2012 18:49, Craig Ringer wrote:
>> When you shut down the 9.1.3 cluster did you make absolutely certain there
>> were no postgres.exe processes lurking around when you tested? Given the
>> incredible thouroughness of your report I
On 22 May 2012 18:49, Craig Ringer wrote:
> When you shut down the 9.1.3 cluster did you make absolutely certain there
> were no postgres.exe processes lurking around when you tested? Given the
> incredible thouroughness of your report I imagine you did, but it's worth
> checking, as a lingering `
First: Best. Bug. Report. Ever.
Comments inline, though I don't know enough about the Windows side to
help much.
Checking for contrib/isn with bigint-passing mismatch ok
Creating catalog dump The
process cannot access the file because it i
(Sending this again to pgsql-bugs with no attachments; hopefully it'll
be accepted. Apologies for any duplicates! I'll provide the
attachments if you need them, though I suspect things may become clear
without them.)
Hello,
I'm forwarding this to pgsql-bugs after sending it to pgsql-testers.
I'
On 05/22/2012 06:28 AM, Edmund Horner wrote:
Hum. My first email sent to this list a few days ago still has not
arrived, so these two are kind of orphaned. Should I resend it?
You mean:
"Just a note that pg_upgrade on Windows 7 64-bit did not have this
error. However, it was a different dat
Hum. My first email sent to this list a few days ago still has not
arrived, so these two are kind of orphaned. Should I resend it?
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 18 May 2012 23:06, Edmund Horner wrote:
> I ran into a bit of trouble running pg_upgrade to upgrade from my
> 9.1.3 cluster. This is the first time I have run pg_upgrade. It is
> entirely possible I've done something wrong.
>
> As a control, I was able to successfully "upgrade" the Postgresq
17 matches
Mail list logo
