aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeHashjoin.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2000-12-30 01:20:55 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2000-12-30 01:20:55 +0000
commitc23851bbe060983cb688afbd9708602fc70fd1d0 (patch)
tree98205c3910bb711e66fa35dbe1174415b943fa48 /src/backend/executor/nodeHashjoin.c
parent2153d1c1062fb8ee363fb186c3cbb2d8533528ba (diff)
downloadpostgresql-c23851bbe060983cb688afbd9708602fc70fd1d0.tar.gz
postgresql-c23851bbe060983cb688afbd9708602fc70fd1d0.zip
Paranoia about possible values of errno after a shmget/semget failure.
In theory we should always get EEXIST if there's a key collision, but if the kernel code tests error conditions in a weird order, perhaps EACCES or EIDRM could occur too.
Diffstat (limited to 'src/backend/executor/nodeHashjoin.c')
0 files changed, 0 insertions, 0 deletions