Stephen Frost <sfr...@snowman.net> writes: > Okay, next user-interface question- thoughts on handling SIGHUP? My > first reaction is that we should create a new log file on SIGHUP (if we > don't already, havn't checked), or maybe just on SIGHUP if this variable > changes.
> Point being, until we get Andrew's jagged-csv-import magic committed to > core, we won't be able to import a log file that a user has changed the > field list for mid-stream (following the add-a-new-column use-case we've > been discussing). Now I think you're reaching the mission-to-mars stage that Robert was complaining about. Solving that sort of problem is well outside the scope of this patch. I don't care if people have to shut down and restart their servers in order to make a change to the log format. Even if I did, the other patch sounds like a better approach. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers