| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
| Cc: | "Steve Crawford" <scrawford(at)pinpointresearch(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Monty on MySQL 5.1: "Oops, we did it again" |
| Date: | 2008-12-01 20:31:26 |
| Message-ID: | dcc563d10812011231r632b8651r691e2d11c2edce7b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2008/12/1 Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>:
> I'd rather do the paritioning by hand and use slony and know it works
> than rely on the code that's doing all that in mysql. If your server
> crashes while updating a partitioned table, you could lose all the
> data in it. Replication can mysteriously just quit working with no
> errors or warning.
>
> Make your pick, half assed code that sometimes works, or postgresql. :)
FYI, my reference up there was to MySQL doing those things (losing
data and not replicating) not pgsql...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2008-12-01 20:32:07 | Re: Trigger before delete does fire before, but delete doesn't not happen |
| Previous Message | Joshua D. Drake | 2008-12-01 20:26:39 | Re: Monty on MySQL 5.1: "Oops, we did it again" |