On 2 Mar 2012, at 15:28, Robert Haas wrote:
On Fri, Mar 2, 2012 at 6:22 AM, Gregg Jaskiewicz gryz...@gmail.com wrote:
Looking at the system bit more now, it look like 'waiting' states are
changing for both the query and autovacuum in pg_stat_activity.
But very slowly. It looks like they both
Wasn't this more of an issue in de-coupling compression from encryption ?
On 25 Jun 2012, at 16:36, Euler Taveira wrote:
On 24-06-2012 23:04, Robert Haas wrote:
So I think we really
need someone to try this both ways and compare. Right now it seems
like we're mostly speculating on how
Hi folks,
I've always been fascinated with genetic algorithms. Having had a chance to
implement it once before, to solve real life issue - I knew they can be
brilliant at searching for right solutions in multi dimensional space.
Thinking about just the postgresql.conf and number of possible
(Resending, I think google mail failed delivering it first time).
Hi folks,
I've always been fascinated with genetic algorithms. Having had a chance to
implement it once before, to solve real life issue - I knew they can be
brilliant at searching for right solutions in multi dimensional
Hi Guys,
Looking around the code Today, one of my helpful tools detected this dead code.
As far as I can see, it is actually unused call to strlen() in formatting.c,
float8_to_char().
Diff attached.
formatting_dead_code.diff
Description: Binary data
--
GJ
--
Sent via
On 7 Apr 2013, at 05:14, Robert Haas robertmh...@gmail.com wrote:
On Thu, Apr 4, 2013 at 6:47 PM, Greg Jaskiewicz gryz...@me.com wrote:
Looking around the code Today, one of my helpful tools detected this dead
code.
As far as I can see, it is actually unused call to strlen() in formatting.c
On 19 Oct 2011, at 17:54, Florian Pflug wrote:
On Oct19, 2011, at 17:47 , Greg Jaskiewicz wrote:
On 15 Oct 2011, at 11:31, Florian Pflug wrote:
Ok, here's a first cut.
So I looked at the patch, and first thing that pops out,
is lack of the volatile keyword before
On 15 Oct 2011, at 11:31, Florian Pflug wrote:
Ok, here's a first cut.
So I looked at the patch, and first thing that pops out,
is lack of the volatile keyword before the ClientConnectionLostPending variable
is defined. Is that done on purpose ? Is that on purpose ?
Otherwise the patch
On 19 Oct 2011, at 18:28, Florian Pflug wrote:
All the other flags which indicate cancellation reasons are set from signal
handers, I believe. We could of course mark as ClientConnectionLostPending as
volatile just to be consistent. Not sure whether that's a good idea, or not.
It might
On 7 Nov 2011, at 15:44, Heikki Linnakangas wrote:
On 07.11.2011 14:01, Gregg Jaskiewicz wrote:
On 7 November 2011 11:57, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
Looks like the range types patch was broken for float timestamps. I'll go
fix that. Thanks for the
Given the amount of fixes that went into the branch, and importance of them -
when can we expect 9.1.2 to be released officially ?
9.1.1 was stamped on 22nd of September.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
On 8 Nov 2011, at 21:23, Kevin Grittner wrote:
This is the time of year when the Wisconsin Courts formalize their
annual plan for where people will be spending the bulk of their time
in the coming year. Two years ago at this time, managers decided
that serializable transactions were a big
On 9 Nov 2011, at 05:06, Magnus Hagander wrote:
I definitely think they are important enough to trigger a release. But as you
say, I think we need confirmation that they actually fix the problem...
Would you consider it a blocker for a rollout on production system ?
On 9 Nov 2011, at 16:16, Robert Haas wrote:
On Wed, Nov 9, 2011 at 11:12 AM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
This commit adds a new warning on my machine:
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=d326d9e8ea1d690cf6d968000efaa5121206d231
copy.c:
On 9 Nov 2011, at 15:33, Peter Geoghegan wrote:
On 9 November 2011 15:24, Tom Lane t...@sss.pgh.pa.us wrote:.
If you go down this road you soon start needing duplicate functions
for no other reason than that one takes/returns const and one doesn't.
Why would you have to do that?
To my
On 16 Nov 2011, at 04:53, Greg Smith wrote:
-Called by specifying includedir directory. No changes to the shipped
postgresql.conf yet.
-Takes an input directory name
Very useful idea.
What will happen if I specify:
includedir './'
Ie, what about potential cyclic dependency.
--
Sent
On 28 Nov 2011, at 02:15, Peter Geoghegan wrote:
Attached are the results from performing a similar process to the
prior benchmark, but on Greg Smith's high-end server, and with an
orderlines table that has been doubled-up until it is 1538 MB,
making the same old query perform a quicksort
Hi masters of PostgreSQL,
I recently got asked about possibility of listening to notifications on warm
standby.
So question, how hard would that be to implement ?
Is it even possible without major changes to the architecture ?
--
Sent via pgsql-hackers mailing list
On 10 Jul 2013, at 19:26, Josh Berkus j...@agliodbs.com wrote:
Huh? LISTEN/NOTIFY across replication has been a desired feature since
we introduced streaming replication. We want it, there's just no
obvious way to do it.
Your email kinda implies that it's not desirable.
Thanks Josh.
19 matches
Mail list logo
