Thread: need help
Hello
pg_dump: server version: 8.1.3; pg_dump version: 8.1.0
pg_dump: proceeding despite version mismatch
pg_dump: DEBUG: StartTransactionCommand
pg_dump: DEBUG: StartTransaction
pg_dump: DEBUG: name: unnamed; blockState: DEFAULT; state: INPROGR, xid/subid/cid: 475771/1/0, nestlvl: 1, children: <>
pg_dump: proceeding despite version mismatch
pg_dump: DEBUG: StartTransactionCommand
pg_dump: DEBUG: StartTransaction
pg_dump: DEBUG: name: unnamed; blockState: DEFAULT; state: INPROGR, xid/subid/cid: 475771/1/0, nestlvl: 1, children: <>
what means here unnamed: blockState is it somekind of big problem or not?
Regards
Andres
<antsumees@hot.ee> writes: > pg_dump: server version: 8.1.3; pg_dump version: 8.1.0 > pg_dump: proceeding despite version mismatch > pg_dump: DEBUG: StartTransactionCommand > pg_dump: DEBUG: StartTransaction > pg_dump: DEBUG: name: unnamed; blockState: DEFAULT; state: = > INPROGR, xid/subid/cid: 475771/1/0, nestlvl: 1, children: <> > what means here unnamed: blockState is it somekind of big problem or = > not? It means you've got logging turned up to an unreasonably high level ;-) There is little point in enabling debug messages if you're not a backend hacker. regards, tom lane