Re: pg_dump 8.0.3 failing against PostgreSQL 7.3.2

Tom Lane wrote:
>
> [ studies 7.3 code a bit ] It might work better to set the breakpoint at
> elog_message_prefix, assuming you've got logging dialed down to the
> point where only actual ERRORs go to the log.

Attaching to process 10284
0x403827df in ?? ()
(gdb) symbol-file postmaster
Reading symbols from postmaster...done.
(gdb) break elog_message_prefix
Breakpoint 1 at 0x16e73f
(gdb) continue
Continuing.

Breakpoint 1, 0x16e73f in elog_message_prefix ()
(gdb) bt
#0 0x16e73f in elog_message_prefix ()
#1 0x16da26 in elog ()
#2 0x82b3d in typecast_expression ()
#3 0x818d9 in transformExpr ()
#4 0x89d4d in transformTargetEntry ()
#5 0x8a021 in transformTargetList ()
#6 0x3cb78 in transformSelectStmt ()
#7 0x3ab6f in transformStmt ()
#8 0x3a79c in parse_analyze ()
#9 0x110574 in pg_analyze_and_rewrite ()
#10 0x110923 in pg_exec_query_string ()
#11 0x112a91 in PostgresMain ()
#12 0xf4eae in DoBackend ()
#13 0xf463d in BackendStartup ()
#14 0xf3040 in ServerLoop ()
#15 0xf2502 in PostmasterMain ()
#16 0xc9926 in main ()
(gdb) detach
Detaching from program: process 10284
(gdb) quit
pgsql(at)hector:/usr/local/pgsql/bin>

Jochem