On 22 May 2012 18:49, Craig Ringer <ring...@ringerc.id.au> 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 `postgres.exe' could (I imagine) cause such an
> issue. Not that it should ever happen.
Yes, I ensured there were no postgres.exe processes running before
running up_upgrade. On a related note, postgres.exe processes DO
remaining running after pg_upgrade fails with this error. Not sure if
they're from the old or new binaries. I generally terminate them and
recreate the destination cluster between retries. Additionally, the
old cluster needs to be cycled: start it, and then stop it; because
the next pg_upgrade run thinks a postgres.exe could still be using it.
pg_ctl start also prints a warning about this but starts anyway.
> Do you have the option of re-trying with your AV disabled or removed?
At work I can't tamper with the AV, but I can run pg_upgrade in a
directory that is excluded from AV (the c:\ccviews directory used by
Clearcase!).
The log files are created there, and there is no AV activity on them
according to Filemon. There is still a SHARING VIOLATION on
pg_upgrade_utility.log, though:
9 3:47:42 p.m. pg_upgrade.exe:97760 OPEN
C:\CCVIEWS\PG_UPGRADE_UTILITY.LOG SUCCESS Options:
Open Access: 00000081
10 3:47:42 p.m. pg_upgrade.exe:97760 QUERY
INFORMATION C:\CCVIEWS\PG_UPGRADE_UTILITY.LOG SUCCESS Length: 179
27 3:47:42 p.m. pg_upgrade.exe:97760 OPEN
C:\ccviews\pg_upgrade_utility.log SUCCESS Options:
OpenIf Access: 00120196
28 3:47:42 p.m. pg_upgrade.exe:97760 QUERY
INFORMATION C:\ccviews\pg_upgrade_utility.log SUCCESS Length: 179
29 3:47:42 p.m. pg_upgrade.exe:97760 QUERY
INFORMATION C:\ccviews\pg_upgrade_utility.log SUCCESS Length: 179
30 3:47:42 p.m. pg_upgrade.exe:97760 WRITE
C:\ccviews\pg_upgrade_utility.log SUCCESS Offset: 179 Length: 179
31 3:47:42 p.m. pg_upgrade.exe:97760 CLOSE
C:\ccviews\pg_upgrade_utility.log SUCCESS
101 3:47:45 p.m. cmd.exe:99028 OPEN
C:\ccviews\pg_upgrade_utility.log SUCCESS Options:
Open Access: 0012019F
102 3:47:45 p.m. cmd.exe:99028 QUERY
INFORMATION C:\ccviews\pg_upgrade_utility.log SUCCESS Length: 358
103 3:47:45 p.m. cmd.exe:99028 QUERY
INFORMATION C:\ccviews\pg_upgrade_utility.log SUCCESS Length: 358
104 3:47:45 p.m. cmd.exe:99028 READ
C:\ccviews\pg_upgrade_utility.log SUCCESS Offset: 357 Length: 1
109 3:47:45 p.m. pg_ctl.exe:98832 WRITE
C:\ccviews\pg_upgrade_utility.log SUCCESS Offset: 358 Length: 30
110 3:47:45 p.m. pg_ctl.exe:98832 WRITE
C:\ccviews\pg_upgrade_utility.log SUCCESS Offset:
388 Length: 1
133 3:47:45 p.m. svchost.exe:560 QUERY
INFORMATION C:\CCVIEWS\PG_UPGRADE_UTILITY.LOG SUCCESS Attributes: A
134 3:47:45 p.m. svchost.exe:560 OPEN
C:\CCVIEWS\PG_UPGRADE_UTILITY.LOG SUCCESS Options:
Open Access: 00020088
135 3:47:45 p.m. svchost.exe:560 QUERY
INFORMATION C:\CCVIEWS\PG_UPGRADE_UTILITY.LOG SUCCESS
FileInternalInformation
136 3:47:45 p.m. svchost.exe:560 CLOSE
C:\CCVIEWS\PG_UPGRADE_UTILITY.LOG SUCCESS
141 3:47:47 p.m. pg_ctl.exe:98832 WRITE
C:\ccviews\pg_upgrade_utility.log SUCCESS Offset: 389 Length: 7
142 3:47:47 p.m. pg_ctl.exe:98832 WRITE
C:\ccviews\pg_upgrade_utility.log SUCCESS Offset: 396 Length: 16
183 3:48:01 p.m. cmd.exe:99396 OPEN
C:\ccviews\pg_upgrade_utility.log SHARING
VIOLATION Options: Open Access: 0012019F
184 3:48:01 p.m. cmd.exe:99396 OPEN
C:\ccviews\pg_upgrade_utility.log SHARING
VIOLATION Options: OpenIf Access: 00120196
195 3:48:02 p.m. cmd.exe:97484 OPEN
C:\ccviews\pg_upgrade_utility.log SHARING
VIOLATION Options: Open Access: 0012019F
196 3:48:02 p.m. cmd.exe:97484 OPEN
C:\ccviews\pg_upgrade_utility.log SHARING
VIOLATION Options: OpenIf Access: 00120196
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
