On Wed, Feb 22, 2012 at 2:31 PM, james ja...@mansionfamily.plus.com wrote:
Has anyone considered managing a system like the DragonFLY swapcache for a
DBMS like PostgreSQL?
https://www.facebook.com/note.php?note_id=388112370932
--
Rob Wultsch
wult...@gmail.com
--
Sent via pgsql-hackers
Excerpts from Noah Misch's message of sáb ene 14 12:20:18 -0300 2012:
Occasionally, I have a SQL file destined for psql's \i command whose name
contains a space. Less often, I'll have a .csv destined for \copy with the
same problem. psql's filename completion does not handle these well. It
2012/2/28 Tom Lane t...@sss.pgh.pa.us:
Christopher Browne cbbro...@gmail.com writes:
On Mon, Feb 27, 2012 at 6:20 PM, Tom Lane t...@sss.pgh.pa.us wrote:
So, whatever the desirability of having them run as table owner,
we can't just up and change that.
I'm inclined to hold to the argument
I noticed a misleading error message recently while using createdb. Try:
test=# CREATE ROLE dummy NOLOGIN;
Now, attempt to use createdb as that role. Here's 9.1.1:
$ createdb -Udummy testdb
createdb: could not connect to database postgres: FATAL: role dummy
is not permitted to log in
And here
On Mon, Feb 27, 2012 at 4:24 AM, Magnus Hagander mag...@hagander.net wrote:
Hi!
I admit to not having actually tested this since I don't have a good
cluster to test it on right now, but from what I can tell the code in
the new checkpointer process only sends statistics to the collector
once
On Feb 27, 2012 10:36 PM, Greg Smith g...@2ndquadrant.com wrote:
One of the reasons I drilled right into this spot is because of fears
that running the writer more often would sprout regressions in TPS. I
can't explain exactly why exactly having backends write their own buffers
out at the latest
On Sun, Feb 26, 2012 at 8:53 AM, Euler Taveira de Oliveira
eu...@timbira.com wrote:
On 25-02-2012 09:23, Magnus Hagander wrote:
Do we even *need* the validate_xlog_location() function? If we just
remove those calls, won't we still catch all the incorrectly formatted
ones in the errors of the
2012/2/28 Tatsuo Ishii is...@postgresql.org:
Are you suggesting log_statement? I don't think it's a solution by
following reasons:
1) it's slow to enable that on busy systems
2) tables affected by cascading delete/update/drop is not logged in
PostgreSQL log
What about reading archived WAL
(2012/02/25 7:31), Peter Eisentraut wrote:
Could we name this postgresql_fdw instead? We already have several
${productname}_fdw out there, and I don't want to get in the business of
having to guess variant spellings.
I worry name conflict with existing postgresql_fdw_validator, which is
On 02/28/2012 04:52 AM, Rob Wultsch wrote:
On Wed, Feb 22, 2012 at 2:31 PM, jamesja...@mansionfamily.plus.com wrote:
Has anyone considered managing a system like the DragonFLY swapcache for a
DBMS like PostgreSQL?
https://www.facebook.com/note.php?note_id=388112370932
in the same vein:
On Tue, Feb 28, 2012 at 12:28 AM, Noah Misch n...@leadboat.com wrote:
On Mon, Feb 27, 2012 at 02:13:32PM +0200, Heikki Linnakangas wrote:
On 23.02.2012 18:01, Alvaro Herrera wrote:
As far as complexity, yeah, it's a lot more complex now -- no question
about that.
How about assigning a new,
101 - 111 of 111 matches
Mail list logo