On Fri, 2011-02-18 at 11:44 +0900, Fujii Masao wrote:
This begs the questions what is the xmin of all the normal
backends?
and Whats is the xmin of prepared transactions? as well. I wasn't
sure that we should expose that information for walsenders when we
don't do it for everybody else.
On 2011-02-18 7:16 AM +0200, Itagaki Takahiro wrote:
Committed with a few typo fixes. Thanks, Marko!
Thanks a lot!
Regards,
Marko Tiikkaja
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
On Fri, 2011-02-18 at 00:48 +, Simon Riggs wrote:
Complete but rough hack, for comments, but nothing surprising.
This is an implicit requirement from our earlier agreed API, so its
blocking further work on Sync Rep.
I'm looking to commit this in about 3-4 hours unless I get comments.
--
Better late than never (or?), here's the final cleanup of
pg_streamrecv for moving into the main distribution, per discussion
back in late dec or early jan. It also includes the stream logs in
parallel to backup part that was not completed on pg_basebackup.
Other than that, the only changes to
Did this ever get applied? If so, I can't find it.
No, my bad, I simply forgot about it, sorry.
Will work on this now.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jabber:
sorry for the late answer. Here is a minimal patch against the
My answer is way later, so I have to apologize.
current GIT tree, so the WHERE CURRENT OF accepts
dynamic cursornames, plus the test case that shows the problem.
It doesn't on my test system. I just committed the minimal patch,
On Fri, Feb 18, 2011 at 02:01, charles.mcdev...@emc.com wrote:
On 02/17/2011 12:34 PM, Bruce Momjian wrote:
Andrew Dunstan wrote:
On 02/17/2011 12:13 PM, Bruce Momjian wrote:
FWIW, the only interactively usable version of psql for windows I know
of is the one that runs under Cygwin. It
On Thu, Feb 17, 2011 at 23:11, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
Dan Ports d...@csail.mit.edu wrote:
Oops. Those are both definitely bugs (and my fault). Your patch
looks correct. Thanks for catching that!
Could a committer please apply the slightly modified version here?:
On Fri, Feb 18, 2011 at 03:57, Robert Haas robertmh...@gmail.com wrote:
On Wed, Feb 16, 2011 at 10:45 PM, Itagaki Takahiro
I am not qualified to fully review this patch because I'm not all that
familiar with the encoding stuff, but it looks reasonably sensible on
a quick read-through. I am
On tor, 2011-02-17 at 17:50 -0500, Tom Lane wrote:
What are we going to do to allow the citext update script to fix this?
I see no sign that ALTER TYPE can fix it (and am unsure that we'd want
to add such a feature, particularly not right now).
How would this normally be handled if a type
UNLOGGED is defigned in OptTemp in gram.y, so the parser accepts
CREATE UNLOGGED VIEW and CREATE UNLOGGED SEQUENCE, but they are
actually not supported.
=# CREATE UNLOGGED VIEW uv AS SELECT 1;
TRAP: FailedAssertion(!(relkind == 'r' || relkind == 't'), File:
heap.c, Line: 1246)
=# CREATE UNLOGGED
We agreed to add a parameter called sync_standbys
http://archives.postgresql.org/message-id/4d1dcf5a.7070...@enterprisedb.com.
that required the concept of a server name.
I've written this patch to add a server name parameter and to send an
info message which returns the server name, attached.
On Fri, Feb 18, 2011 at 6:34 AM, Simon Riggs si...@2ndquadrant.com wrote:
Separate messages for standby replies and hot standby feedback.
Allow messages to be sent at different times, and greatly reduce
the frequency of hot standby feedback. Refactor to allow additional
message types.
You
On Thu, Feb 17, 2011 at 10:37 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Gan Jiadong ga...@huawei.com writes:
we have PG 8.3.13 in our system. When running performance cases, we find the
startup recovery cost about 3 minutes. It is too long in our system.
Maybe you should rethink the assumption
.
* The comment in fileIterate seems wrong. It should be
/* Store the next tuple as a virtual tuple. */ , right?
* #include sys/stat.h is needed.
Fixed all of above.
Regards,
--
Shigeru Hanada
20110218-file_fdw.patch.gz
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers
On Thu, Feb 17, 2011 at 9:13 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I wrote:
Robert Haas robertmh...@gmail.com writes:
I think we should try to make the state match as closely as possible,
no matter how you got there. Otherwise, I think we're storing up a
host of future pain for ourselves.
On Thu, Feb 17, 2011 at 10:40 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Thu, Feb 17, 2011 at 4:53 PM, Tom Lane t...@sss.pgh.pa.us wrote:
In short, add a bit of overhead at SetUserId time in order to make this
cheap (and accurate) in elog.c.
As
On Thu, Feb 17, 2011 at 10:17 PM, Mark Kirkwood
mark.kirkw...@catalyst.net.nz wrote:
This is WIP, it does seem to work ok, but some areas/choices I'm not
entirely clear about are mentioned in the patch itself. Mainly:
- name of the guc... better suggestions welcome
- datatype for the guc -
On Fri, Feb 18, 2011 at 6:42 AM, Itagaki Takahiro
itagaki.takah...@gmail.com wrote:
UNLOGGED is defigned in OptTemp in gram.y, so the parser accepts
CREATE UNLOGGED VIEW and CREATE UNLOGGED SEQUENCE, but they are
actually not supported.
=# CREATE UNLOGGED VIEW uv AS SELECT 1;
TRAP:
On Fri, 2011-02-18 at 07:11 -0500, Robert Haas wrote:
On Fri, Feb 18, 2011 at 6:34 AM, Simon Riggs si...@2ndquadrant.com wrote:
Separate messages for standby replies and hot standby feedback.
Allow messages to be sent at different times, and greatly reduce
the frequency of hot standby
Robert Haas robertmh...@gmail.com writes:
Possibly, but it's not necessarily a bad idea to improve performance
for people with crazy schemas.
It is if it introduces unmaintainable code. I see no way to collapse
multiple drop operations into one that's not going to be a Rube Goldberg
device.
Robert Haas robertmh...@gmail.com writes:
On Fri, Feb 18, 2011 at 6:42 AM, Itagaki Takahiro
The most easiest fix would be preventing them in parser level.
Well, that sucks. I had intended for that to be disallowed at the
parser level, but obviously I fail. It seems that disallowing this in
On Fri, Feb 18, 2011 at 2:27 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 17.02.2011 14:30, Gurjeet Singh wrote:
On Wed, Feb 16, 2011 at 6:37 PM, Tom Lanet...@sss.pgh.pa.us wrote:
Fetch the values you need and stuff 'em in the struct. Don't expect
relcache to do
On Fri, Feb 18, 2011 at 10:09 AM, Simon Riggs si...@2ndquadrant.com wrote:
Make a hard state change from catchup to streaming mode.
More useful state change for monitoring purposes, plus a
required change for synchronous replication patch.
As far as I can see, this patch was not posted or
Robert Haas robertmh...@gmail.com wrote:
Simon Riggs si...@2ndquadrant.com wrote:
Make a hard state change from catchup to streaming mode.
More useful state change for monitoring purposes, plus a
required change for synchronous replication patch.
As far as I can see, this patch was not
Robert Haas robertmh...@gmail.com writes:
On Fri, Feb 18, 2011 at 10:09 AM, Simon Riggs si...@2ndquadrant.com wrote:
Make a hard state change from catchup to streaming mode.
More useful state change for monitoring purposes, plus a
required change for synchronous replication patch.
As far as
On 02/17/2011 04:09 PM, Martijn van Oosterhout wrote:
On Wed, Feb 16, 2011 at 04:33:19PM -0800, Joshua D. Drake wrote:
Maybe we really should consider moving to NSS insread?
http://www.mozilla.org/projects/security/pki/nss/
If it solves the license problem, it is well supported etc..
For
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
On 15.02.2011 23:00, Tom Lane wrote:
I think moving the error check downstream would be a good thing.
Ok, I tried moving the error checks to preprocess_rowmarks().
Unfortunately RelOptInfos haven't been built at that stage yet,
Andrew Dunstan and...@dunslane.net writes:
On 02/17/2011 04:09 PM, Martijn van Oosterhout wrote:
This is supported. Where it goes wonky is that this also has to work
when the connection is via SSL. So libpq provides a function to return
(via a void*) a pointer to the OpenSSL structure so that
On Fri, Feb 18, 2011 at 16:51, Tom Lane t...@sss.pgh.pa.us wrote:
Andrew Dunstan and...@dunslane.net writes:
On 02/17/2011 04:09 PM, Martijn van Oosterhout wrote:
This is supported. Where it goes wonky is that this also has to work
when the connection is via SSL. So libpq provides a function
On Fri, 2011-02-18 at 10:41 -0500, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Feb 18, 2011 at 10:09 AM, Simon Riggs si...@2ndquadrant.com wrote:
Make a hard state change from catchup to streaming mode.
More useful state change for monitoring purposes, plus a
Looking into this patch.
--
Álvaro Herrera alvhe...@commandprompt.com
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
Roman Prykhodchenko rprikhodche...@gmail.com wrote:
My students have to make their science projects during this
half-year. I would like to involve some of them in PostgreSQL to
give them an opportunity to work on a real project instead of
writing their own equation solvers or any other
Peter Eisentraut pete...@gmx.net writes:
On tor, 2011-02-17 at 17:50 -0500, Tom Lane wrote:
Is it time for a direct UPDATE on the pg_type row? If so, to what? I see
pg_type.typcollation is supposed to be an OID, so how the heck does
one map a bool CREATE TYPE parameter into the catalog
On Fri, Feb 18, 2011 at 10:41 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Feb 18, 2011 at 10:09 AM, Simon Riggs si...@2ndquadrant.com wrote:
Make a hard state change from catchup to streaming mode.
More useful state change for monitoring purposes,
Robert Haas robertmh...@gmail.com writes:
On Thu, Feb 17, 2011 at 9:13 PM, Tom Lane t...@sss.pgh.pa.us wrote:
2. intarray and tsearch2 use some core support functions in their
GIN opclasses, and those support functions changed signatures in 9.1.
The current solution to this involves having
On Fri, Feb 18, 2011 at 10:56 AM, Simon Riggs si...@2ndquadrant.com wrote:
We need a hard state change at one particular point to avoid sync rep
requestors from hanging for hours when the standby is connected but a
long way from being caught up.
That's a matter of opinion. I think there are a
On Fri, Feb 18, 2011 at 12:01 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Thu, Feb 17, 2011 at 9:13 PM, Tom Lane t...@sss.pgh.pa.us wrote:
2. intarray and tsearch2 use some core support functions in their
GIN opclasses, and those support functions
Robert Haas robertmh...@gmail.com writes:
On Fri, Feb 18, 2011 at 12:01 PM, Tom Lane t...@sss.pgh.pa.us wrote:
OK, I held my nose and inserted UPDATE commands to make the opclasses
match. AFAICT the only remaining discrepancy between contrib modules
made fresh in 9.1 and those updated from
On 18.02.2011 17:02, Gurjeet Singh wrote:
On Fri, Feb 18, 2011 at 2:27 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 17.02.2011 14:30, Gurjeet Singh wrote:
On Wed, Feb 16, 2011 at 6:37 PM, Tom Lanet...@sss.pgh.pa.us wrote:
Fetch the values you need and stuff 'em in
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
On 18.02.2011 17:02, Gurjeet Singh wrote:
On Wed, Feb 16, 2011 at 6:37 PM, Tom Lanet...@sss.pgh.pa.us wrote:
Fetch the values you need and stuff 'em in the struct. Don't expect
relcache to do it for you.
I also wish to make
Hackers,
I have following proposal. Currently the ts_typanalyze function accumulates
frequency statistics for ts_vector using lossy counting technique. But no
frequency statistics is collecting over arrays. I'm going to generalize
ts_typanalyze to make it collecting statistics for arrays too.
Alexander Korotkov aekorot...@gmail.com writes:
I have following proposal. Currently the ts_typanalyze function accumulates
frequency statistics for ts_vector using lossy counting technique. But no
frequency statistics is collecting over arrays. I'm going to generalize
ts_typanalyze to make it
On Fri, Feb 18, 2011 at 10:02 AM, Tom Lane t...@sss.pgh.pa.us wrote:
If by the first option you mean causing the failure report to be syntax
error rather than anything more specific, then I agree that option
sucks. I'd actually vote for putting the error test somewhere in
statement execution
[this time from the right address - apologies if we get a duplicate]
PostgreSQL Experts Inc has a client with a 9.0.2 streaming replication server
that somehow becomes wedged after running for some time.
The server is running as a warm standby, and the client's application
tries to connect to
Robert Haas robertmh...@gmail.com writes:
OK. Proposed patch attached. It looks to me like an unlogged view is
inherently nonsensical, whereas an unlogged sequence is sensible but
we don't implement it (and may never implement it, absent some
evidence that the overhead of WAL logging
On Fri, Feb 18, 2011 at 10:47 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
On 15.02.2011 23:00, Tom Lane wrote:
I think moving the error check downstream would be a good thing.
Ok, I tried moving the error checks to
Andrew Dunstan and...@dunslane.net writes:
The symptom is that the recovery process blocks forever on a semaphore.
We've crashed it and got the following backtrace:
#0 0x003493ed5337 in semop () from /lib64/libc.so.6
#1 0x005bd103 in PGSemaphoreLock (sema=0x2b14986aec38,
On Fri, Feb 18, 2011 at 2:17 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
OK. Proposed patch attached. It looks to me like an unlogged view is
inherently nonsensical, whereas an unlogged sequence is sensible but
we don't implement it (and may never
Tom Kevin,
thank you for your replies. Kevin, I had already employed all the
tricks you mention, except using temporary tables which would be hard
for me due to the structure of my application (but I could try using
something like pgbouncer or so), but thanks a lot for sharing the ideas.
Magnus Hagander wrote:
Better late than never (or?), here's the final cleanup of
pg_streamrecv for moving into the main distribution, per discussion
back in late dec or early jan. It also includes the stream logs in
parallel to backup part that was not completed on pg_basebackup.
Other than
On Fri, Feb 18, 2011 at 2:16 PM, Andrew Dunstan and...@dunslane.net wrote:
I'm not quite sure where to start digging. Has anyone else seen
something similar? Our consultant reports having seen a similar problem
elsewhere, at a client who was running hot standby on 9.0.1, but the
problem did
Robert Haas robertmh...@gmail.com writes:
On Fri, Feb 18, 2011 at 10:47 AM, Tom Lane t...@sss.pgh.pa.us wrote:
The main downside of that is that relation relkinds would have
to become fixed (because there would be no practical way of updating
RTEs in stored rules), which means the convert
On 02/18/2011 02:23 PM, Tom Lane wrote:
Andrew Dunstanand...@dunslane.net writes:
The symptom is that the recovery process blocks forever on a semaphore.
We've crashed it and got the following backtrace:
#0 0x003493ed5337 in semop () from /lib64/libc.so.6
#1
Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
On 02/17/2011 04:09 PM, Martijn van Oosterhout wrote:
This is supported. Where it goes wonky is that this also has to work
when the connection is via SSL. So libpq provides a function to return
(via a void*) a pointer to the
Robert Haas robertmh...@gmail.com writes:
On Fri, Feb 18, 2011 at 2:17 PM, Tom Lane t...@sss.pgh.pa.us wrote:
+1 for where you put the tests, but I don't think
ERRCODE_SYNTAX_ERROR is an appropriate errcode. I'd go with
FEATURE_NOT_SUPPORTED for both, I think.
I hesitate to use
Frederik Ramm frede...@remote.org writes:
The single query where pg9.0 beat pg8.3 by a country mile was a CREATE
INDEX statement on a BIGINT column to a table with about 500 million
records - this cost 2679 seconds on normal 8.3, 2443 seconds on
large-memory 8.3, and aroung 1650 seconds on
Mark,
I got to wonder how hard this would be to do in Postgres, and attached
is my (WIP) attempt. It provides a guc (max_temp_files_size) to limit
the size of all temp files for a backend and amends fd.c cancel
execution if the total size of temporary files exceeds this.
First, are we just
On Fri, Feb 18, 2011 at 2:35 PM, Andrew Dunstan and...@dunslane.net wrote:
It's not running HS, so there's no query to wait on.
That seems to imply that recovery has leaked a buffer pin.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via
On Fri, Feb 18, 2011 at 2:41 PM, Josh Berkus j...@agliodbs.com wrote:
Second, the main issue with these sorts of macro-counters has generally
been their locking effect on concurrent activity. Have you been able to
run any tests which try to run lots of small externally-sorted queries
at once
On 2/18/11 11:44 AM, Robert Haas wrote:
On Fri, Feb 18, 2011 at 2:41 PM, Josh Berkus j...@agliodbs.com wrote:
Second, the main issue with these sorts of macro-counters has generally
been their locking effect on concurrent activity. Have you been able to
run any tests which try to run lots of
Robert Haas robertmh...@gmail.com writes:
On Fri, Feb 18, 2011 at 2:35 PM, Andrew Dunstan and...@dunslane.net wrote:
It's not running HS, so there's no query to wait on.
That seems to imply that recovery has leaked a buffer pin.
No, because then the sanity check in LockBufferForCleanup would
I have two questions:
1. why are you using the expansible char array stuff instead of using
the StringInfo facility?
2. is md5 the most appropriate digest for this? If you need a
cryptographically secure hash, do we need something stronger? If not,
why not just use hash_any?
--
Álvaro
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Another version, rebased against master branch and with a bunch of small
cosmetic fixes.
I guess this is as good as this is going to get for 9.1.
This is *badly* in need of another cleanup pass; it's full of typos,
contradictory
Tom Lane t...@sss.pgh.pa.us writes:
OK. Thanks for nailing all of this down - that's got to have been a
heck of a job.
+1
Yeah, it was a bit of a pain, and took longer than I would've hoped.
Well, with some luck (and effort) 9.2 will have the missing DDL pieces.
I think the extension
On 18.02.2011 22:16, Tom Lane wrote:
Heikki Linnakangasheikki.linnakan...@enterprisedb.com writes:
Another version, rebased against master branch and with a bunch of small
cosmetic fixes.
I guess this is as good as this is going to get for 9.1.
This is *badly* in need of another cleanup
PostgreSQL Experts Inc has a client with a 9.0.2 streaming replication
server that somehow becomes wedged after running for some time.
The server is running as a warm standby, and the client's application
tries to connect to both the master and the slave, accepting whichever
lets it connect
On Fri, Feb 18, 2011 at 2:48 PM, Josh Berkus j...@agliodbs.com wrote:
On 2/18/11 11:44 AM, Robert Haas wrote:
On Fri, Feb 18, 2011 at 2:41 PM, Josh Berkus j...@agliodbs.com wrote:
Second, the main issue with these sorts of macro-counters has generally
been their locking effect on concurrent
On Fri, Feb 18, 2011 at 2:50 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Feb 18, 2011 at 2:35 PM, Andrew Dunstan and...@dunslane.net wrote:
It's not running HS, so there's no query to wait on.
That seems to imply that recovery has leaked a buffer
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
On 18.02.2011 22:16, Tom Lane wrote:
Question after first look: what is the motivation for passing
estate-es_param_list_info to BeginScan? AFAICS, even if there is a
reason for that function to need that, it isn't receiving any
On 19/02/11 02:34, Robert Haas wrote:
Please add this to the next CommitFest:
https://commitfest.postgresql.org/action/commitfest_view/open
With respect to the datatype of the GUC, int seems clearly correct.
Why would you want to use a float?
Added. With respect to the datatype, using int
On 19/02/11 08:48, Josh Berkus wrote:
On 2/18/11 11:44 AM, Robert Haas wrote:
On Fri, Feb 18, 2011 at 2:41 PM, Josh Berkusj...@agliodbs.com wrote:
Second, the main issue with these sorts of macro-counters has generally
been their locking effect on concurrent activity. Have you been able to
Obviously you need to do the same sort of arithmetic as you do with
work_mem to decide on a reasonable limit to cope with multiple users
creating temp files. Conservative dbas might want to set it to (free
disk)/max_connections etc. Obviously for ad-hoc systems it is a bit more
challenging -
Mark Kirkwood mark.kirkw...@catalyst.net.nz writes:
Added. With respect to the datatype, using int with KB units means the
largest temp size is approx 2047GB - I know that seems like a lot now...
but maybe someone out there wants (say) their temp files limited to
4096GB :-)
[ shrug... ]
Did we make any progress on this? Is it a TODO?
---
Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
On Sun, Aug 15, 2010 at 9:25 PM, Tom Lane t...@sss.pgh.pa.us wrote:
... and PANIC is absolutely, entirely,
Bruce Momjian br...@momjian.us writes:
Did we make any progress on this? Is it a TODO?
AFAIR nothing's been done about it, so it's a TODO.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
On Fri, Feb 18, 2011 at 4:46 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Bruce Momjian br...@momjian.us writes:
Did we make any progress on this? Is it a TODO?
AFAIR nothing's been done about it, so it's a TODO.
I was thinking of adding it to the 9.1 open items list, but the wiki's
been down
Robert Haas wrote:
On Fri, Feb 18, 2011 at 4:46 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Bruce Momjian br...@momjian.us writes:
Did we make any progress on this? ?Is it a TODO?
AFAIR nothing's been done about it, so it's a TODO.
I was thinking of adding it to the 9.1 open items list, but
On 19/02/11 10:38, Josh Berkus wrote:
To answer the other question, what happens when the limit is exceeded is
modeled on statement timeout, i.e query is canceled and a message says
why (exceeded temp files size).
When does this happen? When you try to allocate the file, or when it
does the
Robert Haas robertmh...@gmail.com writes:
On Fri, Feb 18, 2011 at 4:46 PM, Tom Lane t...@sss.pgh.pa.us wrote:
AFAIR nothing's been done about it, so it's a TODO.
I was thinking of adding it to the 9.1 open items list, but the wiki's
been down every time I've tried to go there.
Since the
On Fri, Feb 18, 2011 at 4:59 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Feb 18, 2011 at 4:46 PM, Tom Lane t...@sss.pgh.pa.us wrote:
AFAIR nothing's been done about it, so it's a TODO.
I was thinking of adding it to the 9.1 open items list, but the
Robert Haas wrote:
On Fri, Feb 18, 2011 at 4:59 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Feb 18, 2011 at 4:46 PM, Tom Lane t...@sss.pgh.pa.us wrote:
AFAIR nothing's been done about it, so it's a TODO.
I was thinking of adding it to the 9.1
On 02/18/2011 03:42 PM, Robert Haas wrote:
On Fri, Feb 18, 2011 at 2:50 PM, Tom Lanet...@sss.pgh.pa.us wrote:
Robert Haasrobertmh...@gmail.com writes:
On Fri, Feb 18, 2011 at 2:35 PM, Andrew Dunstanand...@dunslane.net wrote:
It's not running HS, so there's no query to wait on.
That
Yeah, the disadvantage is that (like statement timeout) it is a 'bottom
of the cliff' type of protection. The advantage is there are no false
positives...
Yeah, just trying to get a handle on the proposed feature. I have no
objections; it seems like a harmless limit for most people, and
On 19/02/11 11:30, Josh Berkus wrote:
Yeah, the disadvantage is that (like statement timeout) it is a 'bottom
of the cliff' type of protection. The advantage is there are no false
positives...
Yeah, just trying to get a handle on the proposed feature. I have no
objections; it seems like a
The CommitFest application currently reflects 17 remaining patches for
CommitFest 2011-01.
1. Change pg_last_xlog_receive_location not to move backwards. We
don't have complete consensus on what to do here. If we can agree on
a way forward, I think we can finish this one up pretty quickly.
On Fri, Feb 18, 2011 at 5:10 PM, Bruce Momjian br...@momjian.us wrote:
Robert Haas wrote:
On Fri, Feb 18, 2011 at 4:59 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Feb 18, 2011 at 4:46 PM, Tom Lane t...@sss.pgh.pa.us wrote:
AFAIR nothing's been
Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
Tom Lane wrote:
I think we have a few TODO items here:
* Invent ... and document ... an API that permits safe assembly of a
parameter list from non-constant (and perhaps untrustworthy) values.
* Fix xslt_process' failure to
Robert Haas robertmh...@gmail.com writes:
3, 4, 5. SQL/MED. Tom has picked up the main FDW API patch, which I
expect means it'll go in. I am not so sure about the FDW patches,
though: in particular, based on Heikki's comments, the postgresql_fdw
patch seems to be badly in need of some more
On 2/18/11 2:47 PM, Robert Haas wrote:
The CommitFest application currently reflects 17 remaining patches for
CommitFest 2011-01.
I'm impressed, actually. This is way further along than I expected us
to be.
--
-- Josh Berkus
On 2/18/11 3:04 PM, Tom Lane wrote:
postgresql_fdw may have to live as an external project for the 9.1
cycle, unless it's in much better shape than you suggest above.
I won't feel too bad about that as long as the core support exists.
More than likely, people would want to improve it on a
On 02/18/2011 05:47 PM, Robert Haas wrote:
3, 4, 5. SQL/MED. Tom has picked up the main FDW API patch, which I
expect means it'll go in. I am not so sure about the FDW patches,
though: in particular, based on Heikki's comments, the postgresql_fdw
patch seems to be badly in need of some more
Josh Berkus j...@agliodbs.com writes:
On 2/18/11 3:04 PM, Tom Lane wrote:
postgresql_fdw may have to live as an external project for the 9.1
cycle, unless it's in much better shape than you suggest above.
I won't feel too bad about that as long as the core support exists.
More than likely,
Robert Haas wrote:
On Fri, Feb 18, 2011 at 5:10 PM, Bruce Momjian br...@momjian.us wrote:
Robert Haas wrote:
On Fri, Feb 18, 2011 at 4:59 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Feb 18, 2011 at 4:46 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I wrote:
... My feeling is it'd be best to pass down
all the information the executor node has got --- probably we should
just pass the ForeignScanState node itself, and leave a void * in that
for FDW-private data, and be done with it. Otherwise we're going to be
adding missed stuff back to
Well, good news all round.
v17 implements what I believe to be the final set of features for sync
rep. This one I'm actually fairly happy with. It can be enjoyed best at
DEBUG3.
The patch is very lite touch on a few areas of code, plus a chunk of
specific code, all on master-side. Pretty
On 19 February 2011 00:06, Simon Riggs si...@2ndquadrant.com wrote:
Well, good news all round.
v17 implements what I believe to be the final set of features for sync
rep. This one I'm actually fairly happy with. It can be enjoyed best at
DEBUG3.
The patch is very lite touch on a few areas
On Fri, 2011-02-18 at 09:41 -0600, Kevin Grittner wrote:
Robert Haas robertmh...@gmail.com wrote:
Simon Riggs si...@2ndquadrant.com wrote:
Make a hard state change from catchup to streaming mode.
More useful state change for monitoring purposes, plus a
required change for synchronous
On Sat, 2011-02-19 at 00:32 +, Thom Brown wrote:
I see the updated patch I provided last time to fix various errata and
spacing issues got lost in the last round of conversations. Maybe
it's safer to provide a patch for the patch.
I'm sorry about that Thom, your changes were and are
On Fri, Feb 18, 2011 at 8:57 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
1. why are you using the expansible char array stuff instead of using
the StringInfo facility?
2. is md5 the most appropriate digest for this? If you need a
cryptographically secure hash, do we need something
1 - 100 of 108 matches
Mail list logo
