| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Release cycle length |
| Date: | 2003-11-18 03:58:59 |
| Message-ID: | 3FB99903.4090809@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-www |
> eg. Someone who just knows how to use postgres could test my upcoming
> COMMENT ON patch. (It's best if I myself do not test it) Someone with
> more skill with a debugger can be asked to test unique hash indexes by
> playing with concurrency, etc.
I forgot to mention that people who just have large, complex production
databases and test servers at their disposal should be given the task of:
1. Dumping their old version database
2. Loading that into the dev version of postgres
3. Dumping that using dev pg_dump
4. Loading that dump back in
5. Dumping it again
6. Diffing 3 and 5
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2003-11-18 04:07:54 | Re: Release cycle length |
| Previous Message | Marc G. Fournier | 2003-11-18 03:46:46 | Re: [HACKERS] Release cycle length |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2003-11-18 04:07:54 | Re: Release cycle length |
| Previous Message | Marc G. Fournier | 2003-11-18 03:46:46 | Re: [HACKERS] Release cycle length |