PgSql
in [SQL]
|
[HACKERS] parser handling of large object OIDs gram.y treats large object identifiers inconsistently. The privileges stuff treats them as IConst: | LARGE_P OBJECT_P Iconst_list { PrivTarget *n = (PrivTarget *) palloc(sizeof(PrivTarget)); n->targtype = ACL_TARGET_OBJECT; ... 9 Jun 2010 22:01
Out of date docs: DISABLE/ENABLE TRIGGER Excerpts from Dean Rasheed's message of dom jun 06 05:11:02 -0400 2010: Hi, I just spotted that the docs for ALTER TABLE .. DISABLE/ENABLE TRIGGER are out of date, now that we have deferrable uniqueness and exclusion constraints. applied, thanks Also, I think that the original comment in the ENA... 9 Jun 2010 14:12
Performance of Bit String Hi, Youre on the wrong list for this. This is not a -hackers (i.e. developer targeted) but a -general (user targeted) question. On Wednesday 09 June 2010 15:11:41 rupendra.chulyadyo(a)gmail.com wrote: I tried to store a BitString of length 2 million in a Postgres table (see code below), but it did not com... 9 Jun 2010 14:12
[HACKERS] Performance of Bit String Hi, I tried to store a BitString of length 2 million in a Postgres table (see code below), but it did not complete even in 3 mins and then I cancelled it. Surprisingly, it only took few seconds when BitString was of length 500K. Is there any restriction of length of BitString or am I missing something he... 9 Jun 2010 13:06
[BUGS] Server crash while trying to read expressionusing pg_get_expr() On 09/06/10 17:34, Tom Lane wrote: Heikki Linnakangas<heikki.linnakangas(a)enterprisedb.com> writes: We have two options: 1. Make pg_get_expr() handle arbitrary (possibly even malicious) input gracefully. 2. Restrict pg_get_expr() to superusers only. I think #1 is a fool's errand. There i... 30 Jun 2010 17:36
pgstatindex still throws ERROR: value "3220078592" is out of range for type integer On Mon, Jun 7, 2010 at 8:30 PM, Takahiro Itagaki <itagaki.takahiro(a)oss.ntt.co.jp> wrote: Dave Cramer <pg(a)fastcrypt.com> wrote: I noted on line 169 that max_avail is still an int ? Where else would it be having problems ? It should not a problem because the local variable only stores byte size... 9 Jun 2010 08:37
walwriter not closing old files Magnus Hagander wrote: I've just applied the attached file to the walwriter, to solve a case when it keeps handles around to old xlog segments, preventing them from actually being removed, and as such also causing alerts in some monitoring systems. Thanks! I wasted some time on these a while back; ... 9 Jun 2010 08:37
[HACKERS] walwriter not closing old files I've just applied the attached file to the walwriter, to solve a case when it keeps handles around to old xlog segments, preventing them from actually being removed, and as such also causing alerts in some monitoring systems. The way to provoke the problem is: 1. Do something that makes the walwriter active. For ... 9 Jun 2010 07:32
failover vs. read only queries > When the trigger file is created while the recovery keeps waiting for the release of the lock by read only queries, it might take a very long time for the standby to become the master. The recovery cannot go ahead until those read only queries have gone away. This would increase the downtime at the fai... 2 Jul 2010 00:25
[HACKERS] failover vs. read only queries Hi, When the trigger file is created while the recovery keeps waiting for the release of the lock by read only queries, it might take a very long time for the standby to become the master. The recovery cannot go ahead until those read only queries have gone away. This would increase the downtime at the failover... 9 Jun 2010 05:21 |