postgres

mirror of https://github.com/postgres/postgres.git synced 2026-06-13 20:25:58 -04:00

Files

T

Tom Lane 16f2eadfab When doing a parallel restore, we must guard against out-of-range dependency

dump IDs, because the array we're using is sized according to the highest
dump ID actually defined in the archive file.  In a partial dump there could
be references to higher dump IDs that weren't dumped.  Treat these the same
as references to in-range IDs that weren't dumped.  (The whole thing is a
bit scary because the missing objects might have been part of dependency
chains, which we won't know about.  Not much we can do though --- throwing
an error is probably overreaction.)

Also, reject parallel restore with pre-1.8 archive version (made by pre-8.0
pg_dump).  In these old versions the dependency entries are OIDs, not dump
IDs, and we don't have enough information to interpret them.

Per bug #5288 from Jon Erdman.

2010-01-19 18:39:19 +00:00

backend

Fix thinko in my recent change to put an explicit argisrow field in NullTest:

2010-01-19 16:33:33 +00:00

bin

When doing a parallel restore, we must guard against out-of-range dependency

2010-01-19 18:39:19 +00:00

include

Add pg_stat_reset_shared('bgwriter') to reset the cluster-wide shared

2010-01-19 14:11:32 +00:00

interfaces

Added correct error handling in DESCRIBE statement processing by Boszormenyi Zoltan <zb@cybertec.at>.