Hi,
I was trying pg_basebackup on head, i used this command:
"""
postgres@jaime:/usr/local/pgsql/9.2$ bin/pg_basebackup -D $PWD/data2
-x stream -P -p 54392
"""
i got this error
"""
19093/19093 kB (100%), 1/1 tablespace
pg_basebackup: streaming header too small: 17
pg_basebackup: child process exi
Hackers,
Just FYI, we're going to have a small reviewfest in San Francisco on the
12th in order to try to jump-start some of the work for CF4.
Who's in charge of this CommitFest?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@
On Sun, Jan 8, 2012 at 8:42 PM, Peter Eisentraut wrote:
> Currently, check constraints are verified whenever a table row is
> updated at all. It seems to me that we could possibly make this quite a
> bit more efficient if we only ran the check constraint expression when
> the update changes a co
On Mon, Dec 19, 2011 at 8:18 PM, Heikki Linnakangas
wrote:
> Double-writes would be a useful option also to reduce the size of WAL that
> needs to be shipped in replication.
>
> Or you could just use a filesystem that does CRCs...
Double writes would reduce the size of WAL and we discussed many
Here is a patch for the following construct, specified in the SQL
standard:
collation for (expr)
returns the collation of the argument. It's similar to pg_typeof.
The SQL standard is not clear on the exact format of the return value.
I went with what ruleutils.c produces, which is useful fo
Stefan Keller writes:
> There seems to exist some opportunities now with GIST which relate to
> geometry/geography types (but not only...):
> 1. Index-only scans on geometry columns with SP-GIST (being able to do
> a "SELECT id FROM my_table WHERE mygeom...;").
Well, if somebody builds an SP-GiST
Tom,
There seems to exist some opportunities now with GIST which relate to
geometry/geography types (but not only...):
1. Index-only scans on geometry columns with SP-GIST (being able to do
a "SELECT id FROM my_table WHERE mygeom...;").
2. Index clustering incuding NULL values (i.e. being able to d
On 01/08/2012 03:42 PM, Peter Eisentraut wrote:
Currently, check constraints are verified whenever a table row is
updated at all. It seems to me that we could possibly make this quite a
bit more efficient if we only ran the check constraint expression when
the update changes a column that is r
On Sun, Jan 8, 2012 at 21:53, Peter Eisentraut wrote:
> I've recently had a possible need for telling pg_basebackup how to
> handle symlinks in the remote data directory, instead of ignoring them,
> which is what currently happens. Possible options were recreating the
> symlink locally (pointing
On Sun, Dec 25, 2011 at 7:48 PM, Robert Haas wrote:
> m01 tps = 631.875547 (including connections establishing)
> x01 tps = 611.443724 (including connections establishing)
> m08 tps = 4573.701237 (including connections establishing)
> x08 tps = 4576.242333 (including connections establishing)
> m
Currently, check constraints are verified whenever a table row is
updated at all. It seems to me that we could possibly make this quite a
bit more efficient if we only ran the check constraint expression when
the update changes a column that is referenced by the constraint
expression. Through dep
When attempting to connect to a non-existent host with psql, the
connection will hang and ^C will not break the attempt. This affects two
places: startup and in interactive mode with \c. During startup, the new
behavior will be to exit psql. In interactive mode, the new behavior
will be to return t
Hi,
The extension mechanism we added in 9.1 is aimed at allowing a fully
integrated contrib management, which was big enough a goal to preclude
doing anything else in its first release.
Now we have it and we can think some more about what features we want
covered, and a pretty obvious one that's
psql tab completion currently only supports the form GRANT privilege ON
something TO someone (and the analogous REVOKE), but not the form GRANT
role TO someone. Here is a patch that attempts to implement the latter.
diff --git i/src/bin/psql/tab-complete.c w/src/bin/psql/tab-complete.c
index 4737
I've recently had a possible need for telling pg_basebackup how to
handle symlinks in the remote data directory, instead of ignoring them,
which is what currently happens. Possible options were recreating the
symlink locally (pointing to a file on the local system) or copying the
file the symlink
On Sat, Jan 7, 2012 at 5:24 AM, Simon Riggs wrote:
> On Fri, Jan 6, 2012 at 10:24 PM, Robert Haas wrote:
>> Five-minute pgbench run, scale factor 100,
>> permanent tables, my usual config settings. Somewhat depressingly,
>> virtually all of the interesting activity still centers around the
>> s
On 01/08/2012 01:19 PM, Oleg Bartunov wrote:
Dave,
The situation with pgshpere is so, that I think we need new developer,
since Janko keep silence :) I wrote him several time, since I wanted
pgsphere now could benefit very much from our KNNGiST feature. This is
number one development from m
Yes, I returned from Nepal a month ago :) I've sent my opinion about
pgsphere in separate message.
Oleg
On Sat, 7 Jan 2012, Jan Urbaski wrote:
- Original message -
On Saturday, January 07, 2012 04:43:43 PM Dave Cramer wrote:
Well I've sent Teodor a personal email asking him if he was
Dave,
The situation with pgshpere is so, that I think we need new developer,
since Janko keep silence :) I wrote him several time, since I wanted
pgsphere now could benefit very much from our KNNGiST feature. This is
number one development from my point of view. I and Teodor have no
time to wo
On Sat, Jan 7, 2012 at 7:19 PM, Jeff Janes wrote:
> I don't know if this is a bug exactly, but it seems pretty unfortunate.
I'll call it a bug and I think it's mine. I've added it to the list of
open items for 9.2
Thanks for testing.
--
Simon Riggs http://www.2ndQuadrant.co
On Wed, Jan 4, 2012 at 11:14 AM, Simon Riggs wrote:
> Not having a freelist at all is probably a simpler way of avoiding the
> lock contention, so I'll happily back that suggestion instead. Patch
> attached, previous patch revoked.
v2 attached with cleanup of some random stuff that crept onto pa
On Sat, Jan 7, 2012 at 5:30 PM, Tom Lane wrote:
> BTW, if you think this is a fatal issue, then I'm afraid it's also
> a fatal objection to your proposal to turn SnapshotNow into an MVCC
> snapshot.
Not just because of this, but I think its the wrong time in the cycle
to be completely rethinking
On 1/8/12, Alex Shulgin wrote:
>
> Jeff Janes writes:
>
>> It looks like it hold the file handles until either is it is killed
>> and restarted, or until they get flushed out of vfd cache (which holds
>> ~1000 files on my machine, so that can be a long time and lot of disk
>> space).
>>
>> I don'
>> I guess you concerned about that expected/select_views_1.out is
>> patched, not expected/select_views.out.
>> I'm not sure the reason why regression test script tries to make diff
>> between results/select_views and expected/select_views_1.out.
>
> select_views.out and select_views_1.out are alt
Hi,
When I look into archive recovery deeply as DBA point of view, I found
that it's difficult to know (1) when the recovery process switched
reading WAL segments files from archive directory to pg_xlog directory,
and (2) whether it succeeded applying the latest WAL segments in the
pg_xlog directo
Recent results from Robert show clog contention is still an issue.
In various discussions Tom noted that pages prior to RecentXmin are
readonly and we might find a way to make use of that fact in providing
different mechanisms or resources.
I've taken that idea and used it to build a second Clog
On Sat, Jan 7, 2012 at 11:09 AM, Simon Riggs wrote:
> On Sat, Jan 7, 2012 at 10:55 AM, Simon Riggs wrote:
>
>> So there isn't any problem with there being incorrect checksums on
>> blocks and you can turn the parameter on and off as often and as
>> easily as you want. I think it can be USERSET bu
27 matches
Mail list logo
