On Sep12, 2011, at 06:30 , George Barnett wrote:
On 10/09/2011, at 1:30 AM, Bernd Helmle wrote:
--On 9. September 2011 10:27:22 -0400 Tom Lane t...@sss.pgh.pa.us wrote:
On the whole I think you'd be better off lobbying your NFS implementors
to provide something closer to the behavior of
On 12/09/2011, at 3:59 PM, Florian Pflug wrote:
If you really meant to say intr there (and not nointr) then that probably
explains the partial writes.
Still, I agree with Noah and Kevin that we ought to deal more gracefully with
this, i.e. resubmit after a partial read() or write().
Hi,
On 2011-09-10 19:50, Marti Raudsepp wrote:
I tried this patch and noticed something weird. This is probably not
intentional:
Indeed, it is not intentional. Will see how I can fix this.
Thank you for trying the patch out!
--
Marko Tiikkajahttp://www.2ndQuadrant.com/
Hello
I started work on proposed check statement option and there are a few questions?
what is sense of this statement for others PL? When we solve a mainly
PL/pgSQL issue, has sense to implement new statement? Isn't a some
problem in our CREATE FUNCTION design? A separation to two steps
should
On Sat, Sep 10, 2011 at 9:47 PM, Joshua Berkus j...@agliodbs.com wrote:
Download numbers for the installers were bordering on noise compared
to the GA builds last time I looked, double figures iirc. I don't
know about the tarballs offhand and can't check ATM.
Can you check when you get a
On 09/11/2011 11:43 PM, Robert Haas wrote:
Second, I'd like to be able to set a minimum number of lines below which the
pager would not be used, something like:
\pset pagerminlines 200
Thoughts?
Gee, why do I feel like we have something like this already?
We do? We control columns,
The attached patch is a portion that we splitted off when we added
pg_shseclabel system catalog.
It enables the control/sepgsql to assign security label on pg_database
objects that are utilized as a basis to compute a default security
label of schema object.
Currently, we have an ugly assumption
* Andrew Dunstan (and...@dunslane.net) wrote:
It's NOT changing that. All this affects is how +groupname is
treated in pg_hba.conf, i.e. do we treat every superuser there as
being a member of every group.
Ah, sorry for the noise, that's fine (and I'm bit suprised it was a
one-liner, guess I
Hi there,
To enable file_fdw to estimate costs of scanning a CSV file more
accurately, I would like to propose a new FDW callback routine,
AnalyzeForeignTable, which allows to ANALYZE command to collect
statistics on a foreign table, and a corresponding file_fdw function,
fileAnalyzeForeignTable.
On mån, 2011-09-12 at 05:26 -0400, Andrew Dunstan wrote:
On 09/11/2011 11:43 PM, Robert Haas wrote:
Second, I'd like to be able to set a minimum number of lines below which
the
pager would not be used, something like:
\pset pagerminlines 200
Thoughts?
Gee, why do I feel
On mån, 2011-09-12 at 16:46 +1000, George Barnett wrote:
On 12/09/2011, at 3:59 PM, Florian Pflug wrote:
If you really meant to say intr there (and not nointr) then that
probably explains the partial writes.
Still, I agree with Noah and Kevin that we ought to deal more gracefully
On Mon, Sep 12, 2011 at 04:46:53PM +1000, George Barnett wrote:
On 12/09/2011, at 3:59 PM, Florian Pflug wrote:
If you really meant to say intr there (and not nointr) then that
probably explains the partial writes.
Still, I agree with Noah and Kevin that we ought to deal more
On 09/12/2011 08:39 AM, Peter Eisentraut wrote:
On mån, 2011-09-12 at 05:26 -0400, Andrew Dunstan wrote:
On 09/11/2011 11:43 PM, Robert Haas wrote:
Second, I'd like to be able to set a minimum number of lines below which the
pager would not be used, something like:
\pset pagerminlines
On sön, 2011-09-11 at 21:21 -0700, David E. Wheeler wrote:
* Column-leve collation support: Peter/Enterprise DB
Column-level collation support already exists.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
On Sep12, 2011, at 14:54 , Peter Eisentraut wrote:
On mån, 2011-09-12 at 16:46 +1000, George Barnett wrote:
On 12/09/2011, at 3:59 PM, Florian Pflug wrote:
Still, I agree with Noah and Kevin that we ought to deal more gracefully
with this, i.e. resubmit after a partial read() or write().
On Sep12, 2011, at 14:54 , k...@rice.edu wrote:
Many, many, many other software packages expect I/O usage to be the same on
an NFS volume and a local disk volume, including Oracle. Coding every
application,
or more likely mis-coding, to handle this gives every application another
chance
to
On 9/12/11 2:23 AM, Dave Page wrote:
Note that these are only numbers from people who click through the
flags pages on the website. We don't have numbers for people who
download directly from the FTP site or a mirror.
I'd say that 1200 downloads of each alpha is pretty significant. If
even
On Mon, Sep 12, 2011 at 5:23 AM, Dave Page dp...@pgadmin.org wrote:
On Sat, Sep 10, 2011 at 9:47 PM, Joshua Berkus j...@agliodbs.com wrote:
Download numbers for the installers were bordering on noise compared
to the GA builds last time I looked, double figures iirc. I don't
know about the
On Sun, Sep 11, 2011 at 11:08 PM, Amit Kapila amit.kap...@huawei.com wrote:
In the approach mentioned in your idea, it mentioned that once after
taking snapshot, only committed XIDs will be updated and sometimes snapshot
itself.
So when the xmin will be updated according to your idea as
On mån, 2011-09-12 at 10:00 -0400, Robert Haas wrote:
I certainly think there is value in pushing an alpha release after
CF4, and maybe even after CF3.
Yes, that makes sense. Although I was surprised to see that the
download numbers dropped off significantly for the later alphas.
Whether or
Pavel Stehule pavel.steh...@gmail.com writes:
I started work on proposed check statement option and there are a few
questions?
what is sense of this statement for others PL?
IMO you should design this as a call to the PL's validator function.
It's not necessary to make other PLs do anything
On Mon, Sep 12, 2011 at 9:39 AM, Florian Pflug f...@phlo.org wrote:
Really, it's not *that* hard to put a retry loop around read and write.
+1. I don't see what we're gaining by digging in our heels on this
one. Retry loops around read() and write() are pretty routine, and I
wouldn't like to
On Mon, Sep 12, 2011 at 10:30 AM, Peter Eisentraut pete...@gmx.net wrote:
On mån, 2011-09-12 at 10:00 -0400, Robert Haas wrote:
I certainly think there is value in pushing an alpha release after
CF4, and maybe even after CF3.
Yes, that makes sense. Although I was surprised to see that the
This works in 9.1, but not in HEAD:
CREATE TABLE parent(id INTEGER, CONSTRAINT id_check CHECK(id1));
CREATE TABLE child() INHERITS(parent);
ALTER TABLE ONLY parent DROP CONSTRAINT id_check;
I'm getting:
ERROR: relation 16456 has non-inherited constraint id_check
where 16456 is the oid of the
On Mon, Sep 12, 2011 at 11:07 AM, Amit Kapila amit.kap...@huawei.com wrote:
If you know what transactions were running the last time a snapshot summary
was written and what transactions have ended since then, you can work out
the new xmin on the fly. I have working code for this and it's
The libpq documentation for PQexec states:
If a null pointer is returned, it should be treated like a
PGRES_FATAL_ERROR result
But this contradicts the example programs; eg. from Example Program 1:
/* Start a transaction block */
res = PQexec(conn, BEGIN);
if (PQresultStatus(res)
Excerpts from Tom Lane's message of sáb sep 10 19:03:23 -0300 2011:
I'm considering inventing a new mcxt.c primitive,
void MemoryContextSetParent(MemoryContext context, MemoryContext new_parent);
which would have the effect of delinking context from its current
parent context and
Writing the release notes is really the main part of the work. Bundling
the release takes 15 minutes, writing the announcement takes 15 minutes
(copy and paste), writing the release notes takes about 2 days.
Yeah, but this shaved a lot of effort/delay off doing the final release
notes.
On Mon, Sep 12, 2011 at 10:40 AM, Mark Hills mark.hi...@framestore.com wrote:
The libpq documentation for PQexec states:
If a null pointer is returned, it should be treated like a
PGRES_FATAL_ERROR result
But this contradicts the example programs; eg. from Example Program 1:
/* Start
Hi,
David E. Wheeler da...@kineticode.com writes:
Thanks to Greg Smith for adding a few bonus ideas I hadn't thought of. What
else have you got? I don't think we necessarily have to limit ourselves to
core features, BTW: projects like PostGIS and pgAdmin are also clearly
popular, and new
On Wed, Aug 31, 2011 at 09:59:18AM +, Srinivas Aji wrote:
The following bug has been logged online:
Bug reference: 6189
Logged by: Srinivas Aji
Email address: srinivas@emc.com
PostgreSQL version: 9.0.4
Operating system: Linux
Description:libpq:
On Sep 12, 2011, at 6:01, Peter Eisentraut pete...@gmx.net wrote:
Column-level collation support already exists.
Yeah, just realized that. I mention to say table or column-level encoding.
Best,
David
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to
On Mon, Sep 12, 2011 at 19:21, David Fetter da...@fetter.org wrote:
On Wed, Aug 31, 2011 at 09:59:18AM +, Srinivas Aji wrote:
The following bug has been logged online:
Bug reference: 6189
Logged by: Srinivas Aji
Email address: srinivas@emc.com
PostgreSQL version:
On mån, 2011-09-12 at 09:43 -0700, Josh Berkus wrote:
Writing the release notes is really the main part of the work. Bundling
the release takes 15 minutes, writing the announcement takes 15 minutes
(copy and paste), writing the release notes takes about 2 days.
Yeah, but this shaved a
On mån, 2011-09-12 at 09:01 -0400, Andrew Dunstan wrote:
On 09/12/2011 08:39 AM, Peter Eisentraut wrote:
On mån, 2011-09-12 at 05:26 -0400, Andrew Dunstan wrote:
On 09/11/2011 11:43 PM, Robert Haas wrote:
Second, I'd like to be able to set a minimum number of lines below which
the
On Mon, Sep 12, 2011 at 07:37:23PM +0200, Magnus Hagander wrote:
On Mon, Sep 12, 2011 at 19:21, David Fetter da...@fetter.org wrote:
On Wed, Aug 31, 2011 at 09:59:18AM +, Srinivas Aji wrote:
The following bug has been logged online:
Bug reference: 6189
Logged by:
Isn't the naming of the xlog files slightly bogus?
We have the following sequence:
000108D000FD
000108D000FE
000108D1
Ignoring that we skip FF for some obscure reason (*), these are
effectively supposed to be 64-bit numbers, chunked into 16MB pieces, so
Excerpts from Alvaro Herrera's message of vie sep 02 13:53:12 -0300 2011:
I wonder if there should be a new header, something like
walsender_internal.h, for stuff like WalSnd and WalSndCtlData struct
defs.
... as in the attached patch.
--
Álvaro Herrera alvhe...@commandprompt.com
The
On ons, 2011-09-07 at 10:00 -0400, Tom Lane wrote:
There has however
been some debate about the exact extent of ignoring bad values during
reload --- currently the theory is ignore the whole file if anything is
wrong, but there's some support for applying all non-bad values as long
as the
On 12.09.2011 21:36, Peter Eisentraut wrote:
PS2: While we're discussing the cleanup of xlog.c, someone daring could
replace XLogRecPtr by a plain uint64 and possibly save hundres of lines
of code and eliminate a lot of the above confusion.
One problem with that is that it would break binary
If you know what transactions were running the last time a snapshot summary
was written and what transactions have ended since then, you can work out
the new xmin on the fly. I have working code for this and it's actually
quite simple.
I believe one method to do same is as follows:
Let us
4. Won't it effect if we don't update xmin everytime and just noting the
committed XIDs. The reason I am asking is that it is used in tuple
visibility check so with new idea in some cases instead of just returning
from begining by checking xmin it has to go through the committed XID list.
I
On Sep 12, 2011, at 10:24 PM, Peter Eisentraut wrote:
On ons, 2011-09-07 at 10:00 -0400, Tom Lane wrote:
There has however
been some debate about the exact extent of ignoring bad values during
reload --- currently the theory is ignore the whole file if anything is
wrong, but there's some
Anyone on all of this?
On 09/09/2011 02:31 PM, Alvaro Herrera wrote:
Excerpts from Alvaro Herrera's message of mar ago 09 13:01:04 -0400 2011:
To implement this, we need to augment MultiXact to store the lock type
that each comprising Xid holds on the tuple. Two bits per Xid are
needed.
On Mon, Sep 12, 2011 at 00:22, Tom Lane t...@sss.pgh.pa.us wrote:
Well, people seem to think that this is worth pursuing, so here's a
couple of thoughts about what needs to be done to get to something
committable.
Thanks, that's exactly the kind of feedback I need.
IMO this is no good
Hi,
First off, I hope this approach is not breaking protocol.
I have seen this feature on the todo list:
http://wiki.postgresql.org/wiki/Todo#Referential_Integrity
It's my understanding that this will allow FK constraints on array
elements, if I'm wrong, please stop me now
If I've assumed
Alvaro Herrera alvhe...@commandprompt.com writes:
Excerpts from Tom Lane's message of sáb sep 10 19:03:23 -0300 2011:
I'm considering inventing a new mcxt.c primitive,
void MemoryContextSetParent(MemoryContext context, MemoryContext new_parent);
which would have the effect of delinking
Marti Raudsepp ma...@juffo.org writes:
On Mon, Sep 12, 2011 at 00:22, Tom Lane t...@sss.pgh.pa.us wrote:
type CacheExpr (that's just the first name that came to mind, maybe
somebody has a better idea)
StableConstExpr? But we can leave the bikeshedding for later :)
Well, FWIW, I found that
Peter Eisentraut pete...@gmx.net writes:
Isn't the naming of the xlog files slightly bogus?
No doubt, but by now there's enough replication-ish third-party code
that knows about them that I'm afraid changing these conventions would
be much more painful than it's worth.
On 12/09/2011 12:12, I wrote:
On 2011-09-10 19:50, Marti Raudsepp wrote:
I tried this patch and noticed something weird. This is probably not
intentional:
Indeed, it is not intentional. Will see how I can fix this.
The attached patch is the best I could come up with. I considered
showing
* David E. Wheeler (da...@kineticode.com) wrote:
Toward the end of the presentation, I'd like to make some suggestions and
offer to do some match-making. I'm thinking primarily of listing some of the
stuff the community would love to see done, along with the names of the folks
and/or
Peter Eisentraut wrote:
On m?n, 2011-09-12 at 09:43 -0700, Josh Berkus wrote:
Writing the release notes is really the main part of the work. Bundling
the release takes 15 minutes, writing the announcement takes 15 minutes
(copy and paste), writing the release notes takes about 2 days.
Hi,
While I took a look at MySQL manual (mainly for checking query cache
functionality), I noticed that MySQL has following syntx:
show like 'foo%';
I think this is usefull for show pool_status command since it has
lengthy output now.
Usage of show pool_status and like will be something
On Tue, Sep 13, 2011 at 3:36 AM, Peter Eisentraut pete...@gmx.net wrote:
The return value of pg_start_backup that currently looks something like
pg_start_backup
-
8D1/C9013758
should really be
08D1C9013758
(perhaps the timeline should be included?)
This change
On Mon, Sep 12, 2011 at 8:39 PM, Bruce Momjian br...@momjian.us wrote:
Peter Eisentraut wrote:
On m?n, 2011-09-12 at 09:43 -0700, Josh Berkus wrote:
Writing the release notes is really the main part of the work. Bundling
the release takes 15 minutes, writing the announcement takes 15
Tatsuo Ishii is...@sraoss.co.jp writes:
While I took a look at MySQL manual (mainly for checking query cache
functionality), I noticed that MySQL has following syntx:
show like 'foo%';
I think this is usefull for show pool_status command since it has
lengthy output now.
Usage of show
On Mon, Sep 12, 2011 at 2:20 PM, David Fetter da...@fetter.org wrote:
Well, too much checking, classically, is a source of denial of
service attacks. It's not a super likely source, but it's a source,
and it'd be better to fix it than leave it lie. :)
You forgot to attach the patch.
--
Tatsuo Ishii is...@sraoss.co.jp writes:
While I took a look at MySQL manual (mainly for checking query cache
functionality), I noticed that MySQL has following syntx:
show like 'foo%';
I think this is usefull for show pool_status command since it has
lengthy output now.
Usage of
On Mon, Sep 12, 2011 at 8:44 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Tue, Sep 13, 2011 at 3:36 AM, Peter Eisentraut pete...@gmx.net wrote:
The return value of pg_start_backup that currently looks something like
pg_start_backup
-
8D1/C9013758
should really be
On Tue, Sep 13, 2011 at 12:18 PM, Jaime Casanova ja...@2ndquadrant.com wrote:
and extending
pg_xlogfile_name() so that it accepts not only LSN but also the timeline?
This idea enables us to get the backup start WAL file name by executing
SELECT pg_xlogfile_name(pg_current_timeline(),
On Sep 13, 2011 2:37 AM, Stephen Frost sfr...@snowman.net wrote:
* David E. Wheeler (da...@kineticode.com) wrote:
Toward the end of the presentation, I'd like to make some suggestions
and offer to do some match-making. I'm thinking primarily of listing some of
the stuff the community would
On Fri, Sep 9, 2011 at 8:27 PM, Magnus Hagander mag...@hagander.net wrote:
If the same parameter is specified in both file, the setting in
recovery.conf
overrides that in postgresql.conf. In this case, SHOW command displays
the settings in postgresql.conf even though they are not used at all.
On 13.09.2011 00:33, Dermot wrote:
I have seen this feature on the todo list:
http://wiki.postgresql.org/wiki/Todo#Referential_Integrity
It's my understanding that this will allow FK constraints on array
elements, if I'm wrong, please stop me now
You're right.
I don't want to discourage
On Sep 12, 2011, at 9:41 PM, Magnus Hagander wrote:
I'm not looking for funding (probably couldn't take it if I was offered
it, heh), so I'm not sure if it should be included, but I'm still
planning to dig into revamping the logging system (if I can ever manage
to get out from under my
4. Won't it effect if we don't update xmin everytime and just noting the
committed XIDs. The reason I am asking is that it is used in tuple
visibility check so with new idea in some cases instead of just returning
from begining by checking xmin it has to go through the committed XID
My interpretation of collation for range types is different than that
for arrays, so I'm presenting it here in case someone has an objection.
An array type has the same typcollation as its element type. This makes
sense, because comparison between arrays are affected by the COLLATE
clause.
On Sat, Sep 10, 2011 at 12:18 AM, Simon Riggs si...@2ndquadrant.com wrote:
On Fri, Sep 9, 2011 at 3:05 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
I have to wonder though, if it wouldn't be less confusing to just get
rid of recovery.conf and use a
67 matches
Mail list logo
