aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-08-28 22:27:48 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2011-08-28 22:28:21 -0400
commitce530adf8e3a483e48a8d98ebe421b6963aa639c (patch)
treef69be39263cb63cb9b670c9ed5981f8cd883f80a /src/backend/access/gist/gistproc.c
parent2719a7478db67d5ec081daa76691892ced04077f (diff)
downloadpostgresql-ce530adf8e3a483e48a8d98ebe421b6963aa639c.tar.gz
postgresql-ce530adf8e3a483e48a8d98ebe421b6963aa639c.zip
Actually, all of parallel restore's limitations should be tested earlier.
On closer inspection, whining in restore_toc_entries_parallel is really much too late for any user-facing error case. The right place to do it is at the start of RestoreArchive(), before we've done anything interesting (suh as trying to DROP all the targets ...) Back-patch to 8.4, where parallel restore was introduced.
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions