On Sun, Mar 6, 2011 at 3:23 AM, Robert Haas wrote:
> On Mon, Feb 28, 2011 at 8:08 AM, Fujii Masao wrote:
>> On Sun, Feb 27, 2011 at 11:52 AM, Fujii Masao wrote:
There are two things that I think are pretty clear. If the receiver
has wal_receiver_status_interval=0, then we should ignor
On Sun, 2011-03-06 at 14:27 +0900, Fujii Masao wrote:
> On Sun, Mar 6, 2011 at 2:59 AM, Robert Haas wrote:
> > On Sat, Mar 5, 2011 at 11:56 AM, Simon Riggs wrote:
> >>> Even though postmaster dies, the waiting backend keeps waiting until
> >>> the timeout expires. Instead, the backends should per
On Sun, 2011-03-06 at 16:58 +0900, Fujii Masao wrote:
> On Sun, Mar 6, 2011 at 4:51 PM, Fujii Masao wrote:
> > One comment; what about introducing built-in function to wake up all the
> > waiting backends? When replication connection is closed, if we STONITH
> > the standby, we can safely (for not
On Sun, 2011-03-06 at 01:58 +0900, Fujii Masao wrote:
> On Sun, Mar 6, 2011 at 12:42 AM, Fujii Masao wrote:
> > New comments;
>
> Another one;
>
> + longtimeout = SyncRepGetWaitTimeout();
>
> + else if (timeout > 0 &&
> + Timestamp
I have improved the check and comments for pg_upgrade when testing for
pre-8.4 toast files in the attached applied patch.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
diff --git a
Right now the backend server has a catalog version number which reports
the version of the system tables and storage format. It would be
helpful if pg_upgrade could access a storage format version number for
plugins like /contrib so it could check to see if the cluster can be
upgraded with the ins
On 3 March 2011 06:33, Andy Colson wrote:
> On 1/23/2011 5:11 AM, Michael Meskes wrote:
>> As I already said when the script was introduced, I would love to have a
>> real
>> perl solution, but I'm not a perl programmer by any means.
>>
>> Michael
>
> I thought Kris was going to work on this, but
On 02/03/11 22:28, Jan Urbański wrote:
> On 01/03/11 22:12, Peter Eisentraut wrote:
>> On tis, 2011-03-01 at 21:10 +0100, Jan Urbański wrote:
>>> So you end up with a context message saying "PL/Python function %s"
>>> and a detail message with the saved detail (if it's present) *and* the
>>> traceb
Should we perhaps add a replication line to the default hba file, the
same way we have for regular connections? IIRC we discussed that as a
sub-sub-sub-point in some previous thread, but never mad a decision...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com
On Sat, Mar 5, 2011 at 7:22 AM, Robert Haas wrote:
> Here's a rough attempt at filtering the post-alpha3 commit log down to
> approximately the set of things worth adding to the alpha4 release
> notes.
>
Seems that support LIKE and ILIKE index searches via contrib/pg_trgm indexes
is not mentione
On Sun, Mar 6, 2011 at 5:26 PM, Simon Riggs wrote:
> On Sun, 2011-03-06 at 16:58 +0900, Fujii Masao wrote:
>> On Sun, Mar 6, 2011 at 4:51 PM, Fujii Masao wrote:
>> > One comment; what about introducing built-in function to wake up all the
>> > waiting backends? When replication connection is clos
On Sun, Mar 6, 2011 at 5:02 PM, Yeb Havinga wrote:
> On Sun, Mar 6, 2011 at 8:58 AM, Fujii Masao wrote:
>>
>> If unfortunately all connection slots are used by backends waiting for
>> replication, we cannot execute such a function. So it makes more sense
>> to introduce something like "pg_ctl sta
El 06/03/2011 03:26, "Simon Riggs" escribió:
>
> On Sun, 2011-03-06 at 16:58 +0900, Fujii Masao wrote:
> > If unfortunately all connection slots are used by backends waiting for
> > replication, we cannot execute such a function. So it makes more sense
> > to introduce something like "pg_ctl stan
Andres Freund writes:
> Ah. Finally after trying to stare down the code for some more time the issue
> is pretty simple.
> -
> fmgr_info_collation(irel->rd_index->indcollation.values[attnum-1],
> + fmgr_info_collation(irel->rd_indcollation[attnum-1],
Good catch ... but
Andres Freund writes:
> -
> fmgr_info_collation(irel->rd_index->indcollation.values[attnum-1],
> + fmgr_info_collation(irel->rd_indcollation[attnum-1],
> locinfo);
BTW, I went ahead and committed this part, since the b
Hi!
If all things go according to plans, we will be moving the VM that
runs commitfest.postgresql.org to new hw+platform tomorrow, in the AM
European time. Expected downtime is just a couple of minutes, and I
will leave the old server still responding but in read-only mode.
Thus, if you get a read
On Mar 6, 2011, at 9:44 AM, Fujii Masao wrote:
> On Sun, Mar 6, 2011 at 5:02 PM, Yeb Havinga wrote:
>> On Sun, Mar 6, 2011 at 8:58 AM, Fujii Masao wrote:
>>>
>>> If unfortunately all connection slots are used by backends waiting for
>>> replication, we cannot execute such a function. So it make
On Mar 5, 2011, at 10:14 AM, Magnus Hagander wrote:
> Should we perhaps add a replication line to the default hba file, the
> same way we have for regular connections? IIRC we discussed that as a
> sub-sub-sub-point in some previous thread, but never mad a decision...
Not sure what the point is.
On ons, 2011-03-02 at 16:00 -0500, Tom Lane wrote:
> That seems like a 100% arbitrary distinction between base types and
> domains, to the detriment of base types, which is odd since in most
> other ways base types are much more flexible than domains.
Well, base types don't support check constrain
On Sun, 2011-03-06 at 16:51 +0900, Fujii Masao wrote:
> One comment; what about introducing built-in function to wake up all the
> waiting backends? When replication connection is closed, if we STONITH
> the standby, we can safely (for not physical data loss but logical one)
> switch the primary t
Magnus Hagander wrote:
> I was reading through ref/set_transaction.sgml and noticed that the
> only documentation of DEFERRABLE is that it's a PostgreSQL language
> extension, not anything about what it actually does. Same for begin
> and start_transaction. I see it described in README-SSI and f
On Fri, 2011-03-04 at 16:57 +0900, Fujii Masao wrote:
> On Wed, Mar 2, 2011 at 11:30 PM, Fujii Masao wrote:
> > On Wed, Mar 2, 2011 at 8:22 PM, Simon Riggs wrote:
> >> The WALSender deliberately does *not* wake waiting users if the standby
> >> disconnects. Doing so would break the whole reason
On Sun, 2011-03-06 at 18:09 -0500, Andrew Dunstan wrote:
>
> On 03/06/2011 05:51 PM, Simon Riggs wrote:
> > Efficient transaction-controlled synchronous replication.
> >
>
> I'm glad this is in, but I thought we agreed NOT to call it "synchronous
> replication".
The discussion on the thread was
On Sat, 2011-03-05 at 21:11 +0100, Yeb Havinga wrote:
> I also got a first first > 1000 tps score
The committed version should be even faster. Would appreciate a retest.
--
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Training and Services
Hi all,
I want to construct an "Composite Index Structure" i.e. a combination of
gist and btree.
What i am thinking is that first creating a Rtree structure that is pointing
to another Btree structure.
For example, Suppose i want to find vehicles between 2 to 4 pm on 14/2/2011
on X road.
I am thi
On 07.03.2011 08:07, Nick Raj wrote:
I want to construct an "Composite Index Structure" i.e. a combination of
gist and btree.
What i am thinking is that first creating a Rtree structure that is pointing
to another Btree structure.
For example, Suppose i want to find vehicles between 2 to 4 pm on
On 07.03.2011 01:28, Simon Riggs wrote:
On Sun, 2011-03-06 at 18:09 -0500, Andrew Dunstan wrote:
On 03/06/2011 05:51 PM, Simon Riggs wrote:
Efficient transaction-controlled synchronous replication.
I'm glad this is in, but I thought we agreed NOT to call it "synchronous
replication".
The d
On Mon, 2011-03-07 at 09:29 +0200, Heikki Linnakangas wrote:
> I presume you didn't make allow_synchronous_standby=off the default
> behavior.
You presume incorrectly.
--
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Training and Services
On 05.03.2011 20:09, Heikki Linnakangas wrote:
So the number of lines has roughly doubled since, and about a quarter
of the 7.3 lines have changed.
Heikki,
Yeah.
Additionally, German language vocabulary changed in computer area.
E.g. today "download" is an official German word - ten years
On 07.03.2011 09:48, Simon Riggs wrote:
On Mon, 2011-03-07 at 09:29 +0200, Heikki Linnakangas wrote:
I presume you didn't make allow_synchronous_standby=off the default
behavior.
Sorry, s/allow_synchronous_standby/allow_standalone_master
You presume incorrectly.
Ok, ok then. Thank you! Lo
30 matches
Mail list logo
