Try to fix spurious DSM failures on Windows.
Apparently, Windows can sometimes return an error code even when the operation actually worked just fine. Rearrange the order of checks according to what appear to be the best practices in this area. Amit Kapila
This commit is contained in:
parent
ed4a26260c
commit
1a81daab8b
@ -693,6 +693,15 @@ dsm_impl_windows(dsm_op op, dsm_handle handle, Size request_size,
|
|||||||
size_high, /* Upper 32 bits of size */
|
size_high, /* Upper 32 bits of size */
|
||||||
size_low, /* Lower 32 bits of size */
|
size_low, /* Lower 32 bits of size */
|
||||||
name);
|
name);
|
||||||
|
if (!hmap)
|
||||||
|
{
|
||||||
|
_dosmaperr(GetLastError());
|
||||||
|
ereport(elevel,
|
||||||
|
(errcode_for_dynamic_shared_memory(),
|
||||||
|
errmsg("could not create shared memory segment \"%s\": %m",
|
||||||
|
name)));
|
||||||
|
return false;
|
||||||
|
}
|
||||||
_dosmaperr(GetLastError());
|
_dosmaperr(GetLastError());
|
||||||
if (errno == EEXIST)
|
if (errno == EEXIST)
|
||||||
{
|
{
|
||||||
@ -711,16 +720,15 @@ dsm_impl_windows(dsm_op op, dsm_handle handle, Size request_size,
|
|||||||
hmap = OpenFileMapping(FILE_MAP_WRITE | FILE_MAP_READ,
|
hmap = OpenFileMapping(FILE_MAP_WRITE | FILE_MAP_READ,
|
||||||
FALSE, /* do not inherit the name */
|
FALSE, /* do not inherit the name */
|
||||||
name); /* name of mapping object */
|
name); /* name of mapping object */
|
||||||
_dosmaperr(GetLastError());
|
if (!hmap)
|
||||||
}
|
{
|
||||||
|
_dosmaperr(GetLastError());
|
||||||
if (!hmap)
|
ereport(elevel,
|
||||||
{
|
(errcode_for_dynamic_shared_memory(),
|
||||||
ereport(elevel,
|
errmsg("could not open shared memory segment \"%s\": %m",
|
||||||
(errcode_for_dynamic_shared_memory(),
|
name)));
|
||||||
errmsg("could not open shared memory segment \"%s\": %m",
|
return false;
|
||||||
name)));
|
}
|
||||||
return false;
|
|
||||||
}
|
}
|
||||||
|
|
||||||
/* Map it. */
|
/* Map it. */
|
||||||
|
Loading…
x
Reference in New Issue
Block a user