Matthew T. O'Connor wrote: > Tom Lane wrote: > > >Bruce Momjian <[EMAIL PROTECTED]> writes: > > > > > >>Should we add a variable that is set from the dump filew that identifies > >>the version of PostgreSQL that generated the dump? > >> SET dumped_version = 7.3 > >> > >> > > > >Is that identifying the backend version, or the pg_dump version? > > > >Without a solid rationale for this, I'd rather not do it. > > > > > > > Why not both? I would also think this info could be used in pg_restore > in some way at some point. Even if if can't, wouldn't it be worth it > just for debugging purposes. Knowing for sure what the backend and > pg_dump versions were could be helpful.
My guess was that this information would allow us to change the behavior of PostgreSQL in the future but allow older dumps to still load. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (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: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
