[GENERAL] details locks
Im work with postgres my questions is,its possible on postgres: for example procpidLocker object_locked user_lockedtypeof lock comand 1 admin fooadmin2 exclusive update... thnks for all Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com
Re: [GENERAL] details locks
I understood 2009/8/28 paulo matadr saddon...@yahoo.com.br Im work with postgres my questions is,its possible on postgres: for example procpidLocker object_locked user_lockedtypeof lock comand 1 admin fooadmin2 exclusive update... thnks for all -- Veja quais são os assuntos do momento no Yahoo! + Buscados: Top 10http://br.rd.yahoo.com/mail/taglines/mail/*http://br.maisbuscados.yahoo.com/- Celebridadeshttp://br.rd.yahoo.com/mail/taglines/mail/*http://br.maisbuscados.yahoo.com/celebridades/- Músicahttp://br.rd.yahoo.com/mail/taglines/mail/*http://br.maisbuscados.yahoo.com/m%C3%BAsica/- Esporteshttp://br.rd.yahoo.com/mail/taglines/mail/*http://br.maisbuscados.yahoo.com/esportes/
[GENERAL] Details on community survey
Regarding the community survey on the website: http://www.postgresql.org/community/ It would be great to have a little more detail about each of the TODO's - what it means, what's in scope, what's out of scope, etc. For example, PITR looks like a popular option, but there is already some PITR functionality in Postgres, so what would this TODO add? Also, there was some talk previously about building a new log-based replication scheme, and I don't see that on the list. Why not? Thanks! --S
Re: [GENERAL] Details on community survey
On Mon, Jun 23, 2008 at 10:29 AM, Shahaf Abileah [EMAIL PROTECTED] wrote: Regarding the community survey on the website: http://www.postgresql.org/community/ It would be great to have a little more detail about each of the TODO's – what it means, what's in scope, what's out of scope, etc. For example, PITR looks like a popular option, but there is already some PITR functionality in Postgres, so what would this TODO add? The entry for PITR is for read only PITR slaves, which is another whole level of functionality on top of the current cold standby PITR we have. Also, there was some talk previously about building a new log-based replication scheme, and I don't see that on the list. Why not? I would think a hot standby / read only PITR would be a log based replication scheme of sorts, but I know what you mean. I think the questions are written for people who are already somewhat familiar with the issues, so they tend to be a bit short on description. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Details
Please see the attached file for details. ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
