First
|
Prev |
Next
|
Last
Pages: 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173
Python 3.1 support Peter Eisentraut <peter_e(a)gmx.net> writes: Here's the patch to support Python >=3.1 with PL/Python. The compatibility code is mostly in line with the usual 2->3 C porting practice and is documented inline. There was considerable debate earlier about whether we wanted to treat Python 3 as a separate PL so ... 14 Dec 2009 14:21
New VACUUM FULL On Tue, 2009-10-27 at 13:55 +0900, Itagaki Takahiro wrote: Here is a patch to support "rewrite" version of VACUUM FULL. It was called "VACUUM REWRITE" in the past disucussin, but I choose the following syntax for now: VACUUM ( FULL [ INPLACE | REPLACE ] ) [ table_name ] The reason is to cont... 2 Feb 2010 16:08
write ahead logging in standby (streaming replication) Fujii Masao <masao.fujii(a)gmail.com> writes: Should the standby also have to follow the WAL rule during recovery? The current patch doesn't care about the write order of the data page and WAL in the standby. So, after both servers fail, restarting the ex-standby by itself might corrupt the data. Surely th... 16 Nov 2009 16:55
total execution time as reported by auto_explain Jaime Casanova <jcasanov(a)systemguards.com.ec> writes: I was using auto_explain to log plans (with analyze option on) from queries that take more than 500ms, something i found i little odd is that the duration says 779ms but actual time says 269ms (almost 3 times lower), maybe some kind of instrumentation cl... 11 Nov 2009 10:08
accent-insensitive rgc.tech wrote: Hello, I would suggest the inclusion an option to create the database accent-insensitive, without need to use functions that in some cases it's slow to return the result. Example: select name from table where name ilike 'jo�o' Yes, this is in the current development branch (8.5)... 10 Nov 2009 09:32
Unicode UTF-8 table formatting for psql textoutput Tom Lane wrote: Greg Stark <gsstark(a)mit.edu> writes: While i agree this looks nicer I wonder what it does to things like excel/gnumeric/ooffice auto-recognizing table layouts and importing files. I'm not sure our old format was so great for this so maybe this is actually an improvement I'm asking... 9 Nov 2009 17:45
Freebsd & autoconf-2.63 abindra(a)u.washington.edu wrote: I downloaded the latest postgresql code via cvs on a FreeBSD 7.2 system. When I try to run autoconf on the source it tells me that I need autoconf-2.63. However the freeBSD ports only has autoconf-6.62. Does anyone have any suggestion on how to resolve this? I posted a ... 6 Nov 2009 15:55
broadcom ""length..acces//plage_menu_drive programme/windows/system32/netstat-p sql_connection128=lineage server;source256 ... 4 Nov 2009 18:38
"ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled Alvaro Herrera <alvherre(a)commandprompt.com> writes: What I thought could have happened is that the table was truncated, and then the sinval message telling that to other backends was not sent due to the rollback. Hmm. So far as I can see, what we need is to make sure the sinval message is sent regar... 10 Nov 2009 15:13
[HACKERS] "ERROR: could not read block 6 ...: read only 0 of 8192 bytes"after autovacuum cancelled A customer of ours recently hit a problem where after an autovacuum was cancelled on a table, the app started getting the message in $subject: ERROR: could not read block 6 of relation 1663/35078/1761966: read only 0 of 8192 bytes (block numbers vary from 1 to 6). Things remained in this state until another a... 4 Nov 2009 14:12 |