First  |  Prev |  Next  |  Last
Pages: 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140
Streaming replication and unfit messages
On Thursday 18 February 2010 06:17:06 Fujii Masao wrote: [2460]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it. [2460]: FATAL: invalid standby closing message type 4 [2460]: LOG: could not send data to client: No connection cou... 18 Feb 2010 09:27
[HACKERS] A thought: should we run pgindent now?
In connection with the recent discussion of changing SearchSysCache call format, Robert espoused the view that right now is the time when there are a minimal number of outstanding patches that would suffer merge problems from an invasive change. That seems correct to me --- although ideally everyone should be thin... 18 Feb 2010 00:41
[HACKERS] Michael Clemmons wants to stay in touch on LinkedIn
LinkedIn ------------ I'd like to add you to my professional network on LinkedIn. - Michael Clemmons Confirm that you know Michael Clemmons https://www.linkedin.com/e/isd/1082803003/uR15HoO8/ ------ (c) 2010, LinkedIn Corporation... 17 Feb 2010 20:12
[HACKERS] NOTIFY/LISTEN on read-only slave?
Our documentation says listen/notify will return an error if executed on the hot standby server: o LISTEN, UNLISTEN, NOTIFY since they currently write to system tables With the listen/notify system now implemented in memory, is this still true? -- Bruce Momjian <bruce(a)momjian.us> http://momjian... 17 Feb 2010 19:04
alpha4 timing
Peter Eisentraut wrote: FYI: 9.0alpha4 will be wrapped tomorrow (Thursday) and released Friday'ish. No much time for a translation update I guess ... -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. -- Sent via pgsql-hackers... 18 Feb 2010 20:44
Large object dumps vs older pg_restore
Tom Lane wrote: [snip] Probably the only way we can make this design work is to bump the archive version number so that older pg_restores will fail. (Whereupon there is no need to rename the entry type BTW.) This is slightly annoying but it's not like we've not done it multiple times before. ... 17 Feb 2010 21:20
Listen/Notify payload and interfaces
On Feb 17, 2010, at 10:04 AM, Greg Sabino Mullane wrote: while (my $notify = $dbh->pg_notifies) { my ($name, $pid, $payload) = @$notify; print qq{I received notice "$name" from PID $pid, payload was "$payload"\n}; } Not sure what you mean by adapting interfaces to send payloads, ... 18 Feb 2010 17:21
default parameters
Robert Haas <robertmhaas(a)gmail.com> writes: According to http://www.postgresql.org/docs/current/interactive/plpgsql-porting.html there are no default parameters in PostgreSQL, but according to http://www.postgresql.org/docs/current/interactive/sql-createfunction.html there are. It looks like this was f... 17 Feb 2010 15:38
[HACKERS] Large object dumps vs older pg_restore
I've been looking at the proposed patch for pg_dump with large objects, and I'm afraid it breaks things even worse than they're broken in HEAD. Currently, when pg_restore is processing a BLOBS item, it emits lo_create() followed by lo_write() calls, and conditionally precedes that by lo_unlink() if --clean was sp... 17 Feb 2010 15:38
log_error_verbosity placement
Applied. --------------------------------------------------------------------------- Bruce Momjian wrote: I just realized that log_error_verbosity is in the wrong section in postgresql.conf and in our manual. It is listed under "When to log" when in fact it should be in the "What to log" section. ... 17 Feb 2010 04:29
First  |  Prev |  Next  |  Last
Pages: 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140