First  |  Prev |  Next  |  Last
Pages: 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146
[HACKERS] knngist patch support
Hello, I noticed this morning that the k nearest neighbor gist patch https://commitfest.postgresql.org/action/patch_view?id=230 was still being considered for inclusion in 9. Sadly, this feature appears to have been dropped from 9. It seems to me that the functionality this brings is one of the most common us... 10 Feb 2010 20:14
[HACKERS] log_error_verbosity function display
Right now, log_error_verbosity displays the source code error location in this format: LOCATION: parserOpenTable, parse_relation.c:858 I think it would be clearer to add '()' next to the function name. We use '() to display function names in our docs and I think using '()' would clarify the output, e.g.: ... 10 Feb 2010 19:06
[PATCH] Output configuration status after ./configurerun.
Alvaro Herrera escreveu: The general idea seems sensible to me. I can't comment on the specifics. +1. A lot of other programs have this summary at the end of configure execution. The problem is that PostgreSQL has too many options. Do we want to list all of them? -- Euler Taveira de Oliveira h... 10 Feb 2010 23:34
[HACKERS] Postgres Triggers issue
I have a strange problem we noticed the other day with triggers. We're running 8.3.3 on Solaris 10 (intel) and have a feed that comes in regularly to populate a table we're working on. The feed works just fine inserting rows however the following trigger stops the feed until we remove the trigger. Any though... 10 Feb 2010 15:41
[PATCH] Output configuration status after ./configure run.
On Wed, Feb 10, 2010 at 07:01:19PM +0200, Priit Laes wrote: It might avoid the 'FFFFUUUUUU, I forgot to enable python support.', after you have waited a while for the build to finish... +1 from me, for that very reason! Ross -- Ross Reedstrom, Ph.D. reedstrm(a)rice.e... 10 Feb 2010 13:25
[PATCH] Output configuration status after ./configure run.
Priit Laes <plaes(a)plaes.org> writes: This patch enables showing configure status at the end of ./configure run and thus makes ./configure process a bit easier to follow (in the sense of what features are actually enabled). I don't think anybody actually reads configure's output anyway, so I'm not sure abou... 12 Feb 2010 06:42
pg_restore --single-transaction and --clean
Takahiro Itagaki <itagaki.takahiro(a)oss.ntt.co.jp> writes: Is it a TODO item to replace "DROP" into "DROP IF EXISTS" for cleanup commands in pg_restore? No. We try to avoid using nonstandard SQL in dumps. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To mak... 10 Feb 2010 12:15
Parameter name standby_mode
Joachim Wieland wrote: We want to teach people that Hot Standby and Streaming Replication are two different features. I'm not sure about that, actually. Now that they're both in the tree, they work nicely together and many users will think of them as one. However, Streaming Replication calls its main ... 5 Apr 2010 14:59
pgsql: Make standby server continuously retry restoringthe next WAL
Fujii Masao wrote: As I pointed out previously, the standby might restore a partially-filled WAL file that is being archived by the primary, and cause a FATAL error. And this happened in my box when I was testing the SR. sby [20088] FATAL: archive file "000000010000000000000087" has wrong size: 14... 10 Feb 2010 03:24
pgsql: Make standby server continuously retry restoring the next WAL
On Thu, Jan 28, 2010 at 12:27 AM, Heikki Linnakangas <heikki(a)postgresql.org> wrote: Log Message: ----------- Make standby server continuously retry restoring the next WAL segment with restore_command, if the connection to the primary server is lost. This ensures that the standby can recover automaticall... 30 Mar 2010 22:57
First  |  Prev |  Next  |  Last
Pages: 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146