- Run pgbench -c 10 -T 100
- Stop postgres with -m immediate
That is a strange test to run, but it would be better if the behavior was
not that one.
Well, I think it's a very legitimate test, not for testing performance, but
testing crash recovery and I use it very often.
Ok, interesting. Now I understand your purpose.
You may consider something like "BEGIN; UPDATE ...; \sleep 100 ms;
COMMIT;" so that a crash is most likely to occur with plenty transactions
in progress but without much load.
--
Fabien.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
