PgSql
in [SQL]
|
Proposal for 9.1: WAL streaming from WAL buffers On Fri, Jun 11, 2010 at 9:14 AM, Fujii Masao <masao.fujii(a)gmail.com> wrote: Thought? Comment? Objection? What happens if the WAL is streamed to the standby and then the master crashes without writing that WAL to disk? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company... 8 Jul 2010 04:48
[HACKERS] Proposal for 9.1: WAL streaming from WAL buffers Hi, In 9.0, walsender reads WAL always from the disk and sends it to the standby. That is, we cannot send WAL until it has been written (and flushed) to the disk. This degrades the performance of synchronous replication very much since a transaction commit must wait for the WAL write time *plus* the replication t... 11 Jun 2010 10:19
PG 9.1 tentative timeline * Pr, Solaiyappan (NSN - IN/Bangalore) (solaiyappan.pr(a)nsn.com) wrote: I understand this is very early to ask this.. but, is there any tentative timeline has been planned / available for the PostgreSQL 9.1 release, like for the alpha or beta releases before the general release? The tentative timeline is "more-or-... 14 Jun 2010 12:53
[HACKERS] PG 9.1 tentative timeline Hi, I understand this is very early to ask this.. but, is there any tentative timeline has been planned / available for the PostgreSQL 9.1 release, like for the alpha or beta releases before the general release? Also, is there any synchronous replication patch planned for the PostgreSQL 9.0 version? Regards, ... 11 Jun 2010 09:13
server authentication over Unix-domain sockets On Sun, May 30, 2010 at 13:00, Peter Eisentraut <peter_e(a)gmx.net> wrote: It has been discussed several times in the past that there is no way for a client to authenticate a server over Unix-domain sockets. �So depending on circumstances, a local user could easily insert his own server and collect passwords ... 9 Jul 2010 02:54
vacuum_defer_cleanup_age On 11/06/10 05:36, Fujii Masao wrote: vacuum_defer_cleanup_age is categorized as "Statement Behavior" parameter in the document. On the other hand, it's categorized as "Hot Standby" one in postgresql.conf. Why do we need to do so? Yeah, there's clearly a mismatch. I think "Hot Standby" is the right place,... 11 Jun 2010 10:19
[HACKERS] vacuum_defer_cleanup_age Hi, vacuum_defer_cleanup_age is categorized as "Statement Behavior" parameter in the document. On the other hand, it's categorized as "Hot Standby" one in postgresql.conf. Why do we need to do so? Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- S... 10 Jun 2010 23:27
Bug / shortcoming in has_*_privilege On Thu, Jun 10, 2010 at 5:54 PM, Jim Nasby <jim(a)nasby.net> wrote: test_us(a)workbook=# select has_table_privilege( 'public', 'test', 'SELECT' ); ERROR: �role "public" does not exist test_us(a)workbook=# So there's no way to see if a particular privilege has been granted to public. ISTM 'public' should be acc... 10 Jun 2010 23:27
ps display "waiting for max_standby_delay" Takahiro Itagaki wrote: Hi, We have codes to change ps display for recovery process during hot standby. The current code always shows max_standby_delay for the message, but how about showing actual waiting time instead? Since DBAs can always get the parameter from postgresql.conf they wrote, so the p... 10 Jun 2010 23:27
[HACKERS] Bug / shortcoming in has_*_privilege test_us(a)workbook=# select has_table_privilege( 'public', 'test', 'SELECT' ); ERROR: role "public" does not exist test_us(a)workbook=# So there's no way to see if a particular privilege has been granted to public. ISTM 'public' should be accepted, since you can't use it as a role name anyway... test_us(a)workbook=... 10 Jun 2010 19:03 |