Jaime Casanova wrote: > - identify some people with the problem and talk to them for: 1) get a > way to reproduce the error (a lot dificult, IIRC we try a few times i > fail to fail) or 2) get their support for test
For back-patching, we'd be maybe even more interested in getting people who *don't* experience the problem to test it, to make sure it doesn't break installations that work without it. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
