On Jun 27, 2012, at 7:34 AM, Robert Haas wrote:
On Wed, Jun 27, 2012 at 12:00 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
So, here's a patch. Instead of using POSIX shmem, I just took the
expedient of using mmap() to map a block of
On Jun 26, 2012, at 5:44 PM, Josh Berkus wrote:
On that, I used to be of the opinion that this is a good compromise (a
small amount of interlock space, plus mostly posix shmem), but I've
heard since then (I think via AgentM indirectly, but I'm not sure)
that there are cases where even the
On Jun 26, 2012, at 6:12 PM, Daniel Farina wrote:
(Emphasis mine).
I don't think that -hackers at the time gave the zero-shmem rationale
much weight (I also was not that happy about the safety mechanism of
that patch), but upon more reflection (and taking into account *other*
software
On 06/26/2012 07:30 PM, Tom Lane wrote:
A.M. age...@themactionfaction.com writes:
On Jun 26, 2012, at 6:12 PM, Daniel Farina wrote:
I'm simply suggesting that for additional benefits it may be worth
thinking about getting around nattach and thus SysV shmem, especially
with regard to safety
On 06/26/2012 07:15 PM, Alvaro Herrera wrote:
Excerpts from Tom Lane's message of mar jun 26 18:58:45 -0400 2012:
Even if you actively try to configure the shmem settings to exactly
fill shmmax (which I concede some installation scripts might do),
it's going to be hard to do because of the 8K
On Mar 7, 2012, at 11:39 PM, Bruce Momjian wrote:
On Thu, Mar 01, 2012 at 09:06:10PM -0500, Bruce Momjian wrote:
OK, combining your and Robert's ideas, how about I have pg_upgrade write
the server log to a file, and the pg_dump output to a file (with its
stderr), and if pg_upgrade fails, I
On Mar 8, 2012, at 10:00 AM, Bruce Momjian wrote:
Yes. I was afraid that continually appending to a log file on every run
would be too confusing. I could do only appends, or number the log
files, that those seemed confusing.
the /tmp directory so that one can compare results if the
On Mar 8, 2012, at 4:37 PM, Peter Eisentraut wrote:
On tor, 2012-03-08 at 10:06 -0500, A.M. wrote:
The only reason I truncate them on start is that I am appending to
them
in many places in the code, and it was easier to just truncate them
on
start rather than to remember where I first
On Feb 29, 2012, at 6:02 PM, Bruce Momjian wrote:
On Wed, Feb 29, 2012 at 04:34:24PM -0500, Robert Haas wrote:
On Tue, Feb 28, 2012 at 9:45 PM, Bruce Momjian br...@momjian.us wrote:
OK, I have implemented both Roberts and Àlvaro's ideas in my patch.
I only add the .old suffix to
On Feb 26, 2012, at 10:39 AM, Peter Eisentraut wrote:
On ons, 2012-02-22 at 10:56 -0500, Andrew Dunstan wrote:
The trouble with leakproof is that it
doesn't point to what it is that's not leaking, which is information
rather than memory, as many might imagine (and I did) without further
On Jan 23, 2012, at 2:49 PM, Tom Lane wrote:
Marko Kreen mark...@gmail.com writes:
[ bytea_output doesn't need to be GUC_REPORT because format is
autodetectable ]
Fair enough. Anyway we're really about two years too late to revisit that.
Btw, it does not seems that per-request
On Jan 23, 2012, at 4:45 PM, Merlin Moncure wrote:
On Mon, Jan 23, 2012 at 2:00 PM, A.M. age...@themactionfaction.com wrote:
One simple way clients could detect the binary encoding at startup would be
to pass known test parameters and match against the returned values. If the
client cannot
On Jun 16, 2011, at 11:51 AM, Heikki Linnakangas wrote:
What's the current state of the POSIX shared memory patch? I grabbed the
patch from
http://archives.postgresql.org/message-id/d9edacf7-53f1-4355-84f8-2e74cd19d...@themactionfaction.com
and it doesn't seem to apply cleanly any more.
On May 5, 2011, at 4:08 PM, Alvaro Herrera wrote:
Excerpts from Peter Geoghegan's message of jue may 05 16:49:25 -0300 2011:
I'll need to take a look at statistics, autovacuum and Logger
processes too, to see if they present more subtle opportunities for
reduced idle power consumption.
On Apr 13, 2011, at 9:30 PM, Robert Haas wrote:
On Wed, Apr 13, 2011 at 6:11 PM, A.M. age...@themactionfaction.com wrote:
I don't see why we need to get rid of SysV shared memory; needing less
of it seems just as good.
1. As long one keeps SysV shared memory around, the postgresql project
On Apr 14, 2011, at 8:22 AM, Florian Weimer wrote:
* Tom Lane:
Well, the fundamental point is that ignoring NFS is not the real
world. We can't tell people not to put data directories on NFS,
and even if we did tell them not to, they'd still do it. And NFS
locking is not trustworthy,
On Apr 13, 2011, at 11:37 PM, Tom Lane wrote:
A.M. age...@themactionfaction.com writes:
1. As long one keeps SysV shared memory around, the postgresql project
has to maintain the annoying platform-specific document on how to
configure the poorly named kernel parameters.
No, if it's just
On Apr 13, 2011, at 8:36 PM, Robert Haas wrote:
I don't see why we need to get rid of SysV shared memory; needing less
of it seems just as good.
1. As long one keeps SysV shared memory around, the postgresql project has to
maintain the annoying platform-specific document on how to configure
On Apr 11, 2011, at 6:06 PM, Robert Haas wrote:
On Sun, Apr 10, 2011 at 5:03 PM, A.M. age...@themactionfaction.com wrote:
To ensure that no two postmasters can startup in the same data directory, I
use fcntl range locking on the data directory lock file, which also works
properly
On Apr 11, 2011, at 7:25 PM, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
On Sun, Apr 10, 2011 at 5:03 PM, A.M. age...@themactionfaction.com wrote:
To ensure that no two postmasters can startup in the same data directory, I
use fcntl range locking on the data directory lock
On Apr 11, 2011, at 7:13 PM, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
On Mon, Apr 11, 2011 at 3:11 PM, A.M. age...@themactionfaction.com wrote:
What do you mean by leakier? The goal here is to extinguish SysV shared
memory for portability and convenience benefits. The mini
On Apr 8, 2011, at 7:20 PM, Alvaro Herrera wrote:
Excerpts from A.M.'s message of mié abr 06 19:08:35 -0300 2011:
That's really strange considering that the new role may not normally
have permission to switch to the original role. How would you handle
the case where the security definer
On Apr 6, 2011, at 5:33 PM, Alvaro Herrera wrote:
Hi,
A customer of ours has for a long time the desire to be able to return
to the previous privilege level (i.e. the caller privs) inside a
SECURITY DEFINER function. I find that this notion is not at all
covered in the SQL standard, yet
On Feb 9, 2011, at 12:25 PM, Robert Haas wrote:
On Wed, Feb 9, 2011 at 10:38 AM, Markus Wanner mar...@bluegap.ch wrote:
On 02/09/2011 04:16 PM, David Fetter wrote:
On Tue, Feb 08, 2011 at 09:09:48PM -0500, Robert Haas wrote:
Frankly, I think this is an example of how our current shared
On Jan 18, 2011, at 3:55 PM, Bruce Momjian wrote:
I have modified test_fsync to use test labels that match wal_sync_method
values, and and added more tests for open_sync with different sizes.
This should make the program easier for novices to understand. Here is
a test run for Ubuntu
On Jan 18, 2011, at 5:16 PM, Bruce Momjian wrote:
A.M. wrote:
On Jan 18, 2011, at 3:55 PM, Bruce Momjian wrote:
I have modified test_fsync to use test labels that match wal_sync_method
values, and and added more tests for open_sync with different sizes.
This should make the program
On Jan 18, 2011, at 5:21 PM, Bruce Momjian wrote:
A.M. wrote:
On Jan 18, 2011, at 5:16 PM, Bruce Momjian wrote:
A.M. wrote:
On Jan 18, 2011, at 3:55 PM, Bruce Momjian wrote:
I have modified test_fsync to use test labels that match wal_sync_method
values, and and added more tests
On Jan 18, 2011, at 5:41 PM, Bruce Momjian wrote:
A.M. wrote:
Because the fastest option may not be syncing to disk. For example,
the only option that makes sense on OS X is fsync_writethrough- it
would be helpful if the tool pointed that out (on OS X only, obviously).
Yes, that would
On Jan 5, 2011, at 2:37 PM, Robert Haas wrote:
On Wed, Jan 5, 2011 at 2:36 PM, Simon Riggs si...@2ndquadrant.com wrote:
The lock strength selected on the master doesn't need to be the same as
the lock strength on the standby. You could quite easily generate AEL
lock records to send to
On Nov 17, 2010, at 4:00 PM, Kevin Grittner wrote:
Robert Haas robertmh...@gmail.com wrote:
OK, so we're proposing a hierarchy like this.
1. PERMANENT (already exists).
2. UNLOGGED (what this patch currently implements).
3. UNSYNCED (future work).
4. GLOBAL TEMPORARY (future
Hello,
It seems that this:
CREATE OR REPLACE FUNCTION test_fsync_speed() RETURNS float AS
'$libdir/test_fsync_speed','\
test_fsync_speed' LANGUAGE C IMMUTABLE STRICT;
is not equivalent to this (note void argument):
CREATE OR REPLACE FUNCTION test_fsync_speed(void) RETURNS float AS
On Oct 21, 2010, at 4:19 PM, Robert Haas wrote:
2010/10/21 Tom Lane t...@sss.pgh.pa.us:
Alvaro Herrera alvhe...@commandprompt.com writes:
Excerpts from Cédric Villemain's message of jue oct 21 16:01:30 -0300 2010:
I agree this is interesting information to get, but wonder how
pg_config can
On Oct 19, 2010, at 11:22 AM, Bruce Momjian wrote:
Greg Smith wrote:
A.M. wrote:
Perhaps a simpler tool could run a basic fsyncs-per-second test and prompt
the DBA to check that the numbers are within the realm of possibility.
This is what the test_fsync utility that already ships
On Oct 7, 2010, at 12:26 PM, Robert Haas wrote:
On Thu, Oct 7, 2010 at 11:45 AM, Greg Smith g...@2ndquadrant.com wrote:
Robert Haas wrote:
Proposed doc patch attached.
Looks accurate to me. I like the additional linking to the Reliability page
you put in there too. Heavily referencing
On Sep 30, 2010, at 5:02 PM, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
Oh, I missed that. Actually, I wasn't really so concerned with
whether his benchmark is correct. I *am* concerned about being broken
out of the box on MacOS X.
Actually, the problem with OSX is that
On Sep 21, 2010, at 11:19 PM, Tom Lane wrote:
Offhand I think I like Andrew's recommendation of a shortlived branch
better. In essence your idea is using the tip of master itself as a
shortlived branch, which is maybe a bit too cute. If you get distracted
and need to do something else for
On Aug 31, 2010, at 5:07 PM, Pavel Stehule wrote:
Hello
attached WIP patch.
I implement only basic format's tags related to SQL: string, value,
literal, sql identifier. These tags are basic, but there are not any
break to implement any other formats or enhance a syntax. The mix with
With 9.0b4, I am testing the new NOTIFY payload feature. One thing I noticed is
that it seems impossible to differentiate at the receiving end from:
NOTIFY test;
and
NOTIFY test,'';
So, it is impossible to differentiate between a notification with an empty
string payload and a notification
On Aug 25, 2010, at 6:49 PM, Tom Lane wrote:
Magnus Hagander mag...@hagander.net writes:
The current mapping used is the same one as on git.postgresql.org (see
attached file).
BTW, I noticed that this list omits several old committers:
Julian Assange pr...@suburbia.net
That is _the_
On Aug 18, 2010, at 9:02 AM, Robert Haas wrote:
On Wed, Aug 18, 2010 at 8:45 AM, Greg Stark st...@mit.edu wrote:
On Tue, Aug 17, 2010 at 11:29 PM, Dave Page dp...@pgadmin.org wrote:
Which is ideal for monitoring your own connection - having the info in
the pg_stat_activity is also valuable
On Jan 7, 2010, at 12:39 PM, Greg Sabino Mullane wrote:
I'm still *very* interested in making a libpq-less pure perl driver,
if anyone feels like funding it, let me know! :)
You mean this one:
http://search.cpan.org/~arc/DBD-PgPP-0.07/lib/DBD/PgPP.pm
?
Cheers,
M
--
Sent via pgsql-hackers
On Dec 9, 2009, at 4:23 PM, Chris Browne wrote:
This is a C front end for the LLVM compiler... I noticed that it
entered Debian/Unstable today:
http://packages.debian.org/sid/main/clang
I thought it would be interesting to see if PostgreSQL compiles with
this, as an alternative
On Nov 11, 2009, at 4:25 PM, Joachim Wieland wrote:
Hi,
Attached is a patch for a new listen/notify implementation.
In a few words, the patch reimplements listen/notify as an slru-
based queue
which works similar to the sinval structure. Essentially it is a
ring buffer on
disk with pages
On Nov 11, 2009, at 10:43 PM, Tom Lane wrote:
Andrew Chernow a...@esilo.com writes:
I thought of a compromise: add the number of times a notification
was
generated (coalesced count+1) to the callback data. That would
satisfy
any backwards compatibility concerns and my use case too!
If
On Jul 25, 2009, at 11:06 AM, Tom Lane wrote:
Sam Mason s...@samason.me.uk writes:
Yes, that seems reasonable. The fact that you're still talking about
confined users is slightly worrying and would seem to imply that
there is still a superuser/normal user divide--it's probably just a
On Jul 13, 2009, at 4:51 PM, decibel wrote:
On Jul 13, 2009, at 2:33 PM, Tom Lane wrote:
Alvaro Herrera alvhe...@commandprompt.com writes:
Tom Lane wrote:
The performance and error recovery implications are unfavorable.
Just how badly do you need this, and for what?
Mainly for debugging.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 27, 2009, at 4:44 PM, Pavel Stehule wrote:
Hello
I am thinking about global temp tables. One possible solution is
creating global temporary table like normal table and in planner stage
check
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 27, 2009, at 5:39 PM, Dimitri Fontaine wrote:
Hi,
Le 27 avr. 09 à 23:32, A.M. a écrit :
When will postgresql offer global temporary tables with data
which are shared among sessions? Such tables are great for
transient data such as web
On Apr 27, 2009, at 6:01 PM, Kevin Grittner wrote:
A.M. age...@themactionfaction.com wrote:
On Apr 27, 2009, at 5:39 PM, Dimitri Fontaine wrote:
Le 27 avr. 09 à 23:32, A.M. a écrit :
When will postgresql offer global temporary tables with data
which are shared among sessions? Such tables
On Mar 11, 2009, at 3:18 PM, Grzegorz Jaskiewicz wrote:
On 11 Mar 2009, at 13:51, Marko Kreen wrote:
Linux kernel is moving to use -Os everywhere. AFAIK their argument
is
that kernel code should not be doing anything CPU-intensive, thus
minimal cache usage is more important than unrolled
On Mar 4, 2009, at 6:07 PM, Josh Berkus wrote:
Andrew,
Back on that track, I'd like to see a facility whereby we could
provide an alias (or synonym, to use a nearby subject) columns and
other objects. That would help to overcome naming glitches without
breaking things quite so much.
On Jan 5, 2009, at 1:16 PM, Stephen R. van den Berg wrote:
Upon reading the DFSG, it seems you have a point...
However...
QuickLZ is dual licensed:
a. Royalty-free-perpetuous-use as part of the PostgreSQL backend or
any derived works of PostgreSQL which link in *at least* 50% of the
On Sep 25, 2008, at 5:50 PM, Chris Browne wrote:
[EMAIL PROTECTED] (Gevik Babakhani) writes:
Advantage of C++ is that it reduce lot of OO code written in
C in PostgreSQL, but it is so big effort to do that without
small gain. It will increase number of bugs. Do not forget
also that C++
On Sep 24, 2008, at 2:38 PM, Josh Berkus wrote:
Peter,
Yeah, but do we even have the slightest bit of information about
what exactly would be required to achieve the required levels? And
whether this patch does it? And whether there would be
alternative, more desirable ways to achieve
On Sep 19, 2008, at 1:42 PM, Robert Haas wrote:
It's too early to vote. :-)
The second and third option have prerequisite.
The purpose of them is to match granularity of access controls
provided by SE-PostgreSQL and native PostgreSQL. However, I have
not seen a clear reason why these
On Jul 28, 2008, at 1:54 PM, Dave Cramer wrote:
On 28-Jul-08, at 12:45 PM, Stephen R. van den Berg wrote:
Dave Cramer wrote:
On 27-Jul-08, at 3:00 PM, Stephen R. van den Berg wrote:
Stephen R. van den Berg wrote:
The driver beats libpq in speed by about 62%.
Anyone interested in taking
On Jul 10, 2008, at 1:20 PM, Fabrízio de Royes Mello wrote:
set pgsql-hackers digest
Postgresql hackers have been successfully digested. *burp*
-M
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
On Apr 22, 2008, at 1:47 PM, Simon Riggs wrote:
On Mon, 2008-04-21 at 22:27 -0400, Gregory Stark wrote:
Simon Riggs [EMAIL PROTECTED] writes:
Unrelated to rule processing, you did read the bit about MERGE and
race
conditions? ISTM that MERGE as it stands isn't very useful for
anything
On Apr 21, 2008, at 4:08 PM, Simon Riggs wrote:
The following two files specify the behaviour of the MERGE statement
and
how it will work in the world of PostgreSQL. In places, this
supercedes
my recent commentary on MERGE, particularly with regard to triggers.
Neither of these files is
On Feb 27, 2008, at 9:11 AM, Florian G. Pflug wrote:
Dimitri Fontaine wrote:
Of course, the backends still have to parse the input given by
pgloader, which only pre-processes data. I'm not sure having the
client prepare the data some more (binary format or whatever) is a
wise idea, as
On Feb 1, 2008, at 10:42 AM, Luke Porter wrote:
All
Is there an interest in developing bitemporal functionality in
PostgreSQL
Regards
Luke
I can only speak for myself, but- definitely! Based on the googling I
did on bitemporal database, I kind of do this already with
PostgreSQL.
On Aug 22, 2007, at 11:10 , Tom Lane wrote:
I notice that the existing tsearch documentation that we've imported
fairly consistently refers to Snowball dictionaries with names like
en_stem, ru_stem, etc. However, CVS HEAD is set up to create them
with names english, russian, etc. As I've
On Jun 26, 2007, at 10:04 , Chris Mair wrote:
Hello,
On the italian list we're discussing a case were a user reportedly
worked around this (i.e. got rid of unwanted cascading calls) by
writing an on insert trigger procedure something on the lines of:
ALTER TABLE tab DISABLE TRIGGER USER;
On Mar 15, 2007, at 11:31 , Ron Mayer wrote:
Josh Berkus wrote:
And then what? dynamically construct all your SQL queries?
Sure, sounds like a simple solution to me...
Not to mention DB security issues. How do you secure your
database when
your web client has DDL access?
So, Edward,
On Mar 3, 2007, at 23:19 , Robert Treat wrote:
A similar idea we've been kicking around would be having a set storage
parameter = nologging option for alter table which would, as it's name
implies, cause the system to ignore writing wal logs for the table,
much like
it does for temp tables
On Feb 26, 2007, at 18:58 , Simon Riggs wrote:
On Mon, 2007-02-26 at 23:25 +, Richard Huxton wrote:
Simon Riggs wrote:
Proposal: Implement a new option for COMMIT, for enhancing
performance,
providing a MySQL-like trade-off between performance and
robustness for
*only* those that
On Feb 23, 2007, at 11:24 , Andreas Pflug wrote:
It probably _can_ never happen, because that would have to be a
one-for-all solution, embracing both centric and distributed
repositories, combining contradictionary goals. So the first
question to
answer is: Will PostgreSQL continue with a
On Thu, July 13, 2006 11:03 am, Jonah H. Harris wrote:
This is my point exactly. As with many things, we keep skirting the
real issue by going with an improve the smaller component approach such
as promote pgfoundry more. I have never seen this approach work, but
maybe someone has an example
On Wed, June 28, 2006 1:14 pm, [EMAIL PROTECTED] wrote:
On Wed, Jun 28, 2006 at 06:39:16PM +0200, Thomas Hallgren wrote:
Instead, I would like to humbly request the inclusion of a UUID
datatype (or an opaque 128 bit datatype) in the core package. It's
increasingly common and some databases
On Mon, June 26, 2006 9:37 am, Mark Woodward wrote:
On 6/24/06, Mark Woodward [EMAIL PROTECTED] wrote:
I originally suggested a methodology for preserving MVCC and everyone
is confusing it as update in place, this isnot what I intended.
Actually, you should've presented your idea as
On Fri, June 23, 2006 9:56 am, Martijn van Oosterhout wrote:
On Fri, Jun 23, 2006 at 03:30:45PM +0200, Csaba Nagy wrote:
It sounds like you have a big problem and you need a big
solution.
Well, Postgres does a decent job as it is. The problem is under peek
load, sometimes it gets bogged
On Thu, June 22, 2006 1:42 pm, Josh Berkus wrote:
Marc,
Sorry folks, my fault ... hit the 'accept' button too fast
So, was Wilbur really as attractive as she claimed?
In all seriousness, it's actually a pretty clever spam ploy.
1) Spam mailing lists of nerdy, desperate guys with
It would be nice to keep the gettimeofday()s wherever they are most useful
on hardware/software where they are cheap. Perhaps a compile-time option?
On Fri, June 9, 2006 11:18 am, Martijn van Oosterhout wrote:
On Fri, Jun 09, 2006 at 10:00:20AM -0400, Tom Lane wrote:
To tell you the truth,
I think what he meant was a separate EXPLAIN-CANCEL message on a
cancel-type connection, which would be completely backwards compatible.
Old clients simply wouldn't be able to use the special EXPLAIN cancel,
just like it is now.
On Thu, June 8, 2006 3:01 pm, Tom Lane wrote:
Gregory Stark [EMAIL
To complete the connection pooling for multiple users, it would be great
to have a protocol level option to change roles semi-permanently (to
reduce permissions). RESET SESSION AUTHORIZATION would then bounce back to
that (new, set) role until another protocol-level role rollback. This
would allow
Could postgres offer at least a read-only view of the data in the interim?
Ordering could be controlled by line number.
On Thu, March 30, 2006 10:14 am, Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
If your pg_hba.conf looks like
hostall all
The author doesn't mention why he got a 600x increase- perhaps he
bypassed the delete triggers which was OK for his situation. I don't
like the notion that an optimization requires additional
privileges...why not detect an unqualified delete and call truncate
instead IFF there are no delete
A simple documentation enhancement request: please provide Fast
Backward/Forward links at the bottom of the page as well.
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's
There doesn't seem to be any way to get error reporting with unique
identifiers for each type of error (or warning or notice). Is this
something planned for the future? Would this be a daunting task because
the various messages are strewn throughout the sources? Would
centralized error strings
79 matches
Mail list logo
