Re: Using RSYNC for replication?
| От | Shridhar Daithankar |
|---|---|
| Тема | Re: Using RSYNC for replication? |
| Дата | |
| Msg-id | 200301291618.24951.shridhar_daithankar@persistent.co.in обсуждение исходный текст |
| Ответ на | Re: Using RSYNC for replication? ("Rick Gigger" <rick@alpinenetworking.com>) |
| Список | pgsql-general |
On Wednesday 29 Jan 2003 2:35 pm, you wrote: > > If it can't do this, then it damn well should. Move clogs and WALs into > each > > database's directory so each is isolated. Put a call into Postgres (psql > > function) to catch up on the logs. Then lock every table from writes > (JIC), > > perform the backup, unlock every table. > > Maybe you should consider using mysql if that is what you want. Mysql > works that way. Each database is entirely encapsulated in it's own > directory. Well, postgresql has each database in it's own directories but WAL and clog are shared. If you want them distint, run different database site on same machine. That would be like oracle. Minimum 4 processes per database. To put it politely, I don't like it. Shridhar
В списке pgsql-general по дате отправления: