Jim C. Nasby wrote: > Watching the discussion about how to handle nextval() and keep it dump > compatible makes me wonder: would it be useful to encode database or > dump version info into dumps? ISTM it would make it much more feasible > to handle changes to how things work automatically.
Yes, we have talked about that, and it would work for pg_dump-generated dumps. What it might not work for cleanly are dumps moved a different way, or application changes, so while it might help in some cases, being able to get things working without the version info is desirable. If we ever get to a case where we _need_ to use it, it would be good to have, just in case. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
