Hello, > I don't think that this is going in the good direction, what was > suggested mainly by Robert was to use a micro-language that would > allow far more extensibility that what you are proposing.
I agree, the micro-language would give far more extensibility. However, as stated ibefore, the previous discussions concluded that GUC was a preferred way because it is more user-friendly. > See for > example [hidden email] > for some ideas. IMO, before writing any patch in this area we should > find a clear consensus on what we want to do. Also, unrelated to this > patch, we should really get first the patch implementing the... Hum... > infrastructure for regression tests regarding replication and > archiving to be able to have actual tests for this feature (working on > it for next CF). We could decide and work on patch for n-sync along with setting up regression test infrastructure. > At quick glance, this looks problematic to me if application_name has an > hyphen. Yes, I overlooked the fact that application name could have a hyphen. This can be modified. Regards, Beena Emerson ----- -- Beena Emerson -- View this message in context: http://postgresql.nabble.com/Support-for-N-synchronous-standby-servers-take-2-tp5849384p5849711.html Sent from the PostgreSQL - hackers mailing list archive at Nabble.com. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
