> On 27 Sep 2017, at 19:47, Peter Eisentraut
> wrote:
>
> At the PGCon Developer Meeting it was agreed[0] to add a list of credits
> to the release notes, including everyone who was mentioned in a commit
> message. I have now completed that list.
Wow, it’s bigger than I expected. Thanks for
On Thu, Aug 17, 2017 at 2:58 PM, Tom Lane wrote:
> Dave Page writes:
> > It's ActiveState Perl 5.8.8. Printing $Config{ccflags} doesn't seem to do
> > anything, but perl -V output is below:
>
> That's weird ... you get nothing from
>
> perl -MConfig -e
26379 Fix alarm() for Windows 2003
26087 Storable 0.1 compatibility
25861 IO::File performace issue
25084 long groups entry could cause memory exhaustion
24699 ICMP_UNREACHABLE handling in Net::Ping
Built under MSWin32
Compiled at Jan 23 2007 15:57:46
@INC:
c:/perl/site/lib
c:/perl/lib
.
C:\Program Files\Microsoft Visual Studio 8\VC>
--
Dave Page
PostgreSQL Core Team
http://www.postgresql.org/
;
> Well, we have various buildfarm machines running perls newer than that,
> eg, crake, with 5.24.1. So I'd say there is something busted about your
> perl installation. Perhaps leftover bits of an older version somewhere?
>
Well crake is a Fedora box - and we have no proble
On Thu, May 4, 2017 at 3:54 PM, Tom Lane wrote:
> Alvaro Herrera writes:
> > Something like the (untested) attached perhaps?
>
> Looks plausible, I'm not in a position to test though.
Sandeep/Paresh - can you test please?
--
Dave Page
Blog: http://pgsnake.blogspot.c
SQL.
> > >
> >
> > What commit added support for it?
>
> I don't think the main build mechanism requires explicit support of new
> versions. configure just checks for some prerequisites.
>
Right - and they were adjusted here: https://git.postgresql.
org/gitweb/?p=post
On Thu, Mar 30, 2017 at 2:24 PM, Simon Riggs wrote:
> On 30 March 2017 at 18:29, Simon Riggs wrote:
>
>> Moving to commit this over the next hour. Last chance...
>
> Done. Great work Dave, thanks everybody.
Thanks Simon.
--
Dave Page
Blog: http://pgsnake.blogspot.com
ir have execute permissions GRANTed to pg_monitor
12) Un-redacted use of the functions underpinning the pg_stat_* views
is available to pg_read_all_stats.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL C
ure freeze immediately thereafter. Last time around
>> we left 2 weeks between CF end and feature freeze; the previous one I
>> think we had the final CF last two months. Not stretch on indefinitely,
>> but we know the final CF for a cycle takes more effort than previous
>>
Hi
On Tue, Mar 28, 2017 at 2:22 PM, Stephen Frost wrote:
> Dave,
>
> * Dave Page (dp...@pgadmin.org) wrote:
>> OK, so before I start hacking again, here's a proposal based on my
>> understanding of folks comments, and so open questions. If I can get
>> agreem
On Tue, Mar 28, 2017 at 1:52 PM, Mark Dilger wrote:
>
>> On Mar 28, 2017, at 9:55 AM, Robert Haas wrote:
>>
>> On Tue, Mar 28, 2017 at 12:47 PM, Dave Page wrote:
>>>> I don't see any precedent in the code for having a hardcoded role, other
>>>
ead_monitoring_stats?
Thanks!
On Tue, Mar 28, 2017 at 1:37 PM, Stephen Frost wrote:
> Greetings,
>
> * Robert Haas (robertmh...@gmail.com) wrote:
>> On Tue, Mar 28, 2017 at 12:47 PM, Dave Page wrote:
>> >> I don't see any precedent in the code for having a hardcoded r
On Tue, Mar 28, 2017 at 12:55 PM, Robert Haas wrote:
> On Tue, Mar 28, 2017 at 12:47 PM, Dave Page wrote:
>>> I don't see any precedent in the code for having a hardcoded role, other
>>> than
>>> superuser, and allowing privileges based on a hardcoded test fo
On Tue, Mar 28, 2017 at 12:04 PM, Mark Dilger wrote:
>
>> On Mar 28, 2017, at 8:34 AM, Dave Page wrote:
>>
>> On Tue, Mar 28, 2017 at 11:31 AM, Peter Eisentraut
>> wrote:
>>> This patch touches the pg_buffercache and pg_freespacemap extensions,
>>&
On Tue, Mar 28, 2017 at 11:39 AM, Peter Eisentraut
wrote:
> On 3/28/17 11:34, Dave Page wrote:
>> On Tue, Mar 28, 2017 at 11:31 AM, Peter Eisentraut
>> wrote:
>>> This patch touches the pg_buffercache and pg_freespacemap extensions,
>>> but there appear to be
our or so in a new version.
Right now I'm waiting for discussion to conclude before updating the
patch again.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing
On Mon, Mar 27, 2017 at 3:51 AM, Simon Riggs wrote:
> On 25 March 2017 at 16:30, Dave Page wrote:
>
>> I believe this and other reasons we've described are exactly why other DBMS'
>> do what we're proposing.
>
> It would help review if you could show som
Hi
> On 25 Mar 2017, at 15:55, Stephen Frost wrote:
>
> Robert,
>
> * Robert Haas (robertmh...@gmail.com) wrote:
>>> On Fri, Mar 24, 2017 at 12:46 PM, Dave Page wrote:
>>>> On Fri, Mar 24, 2017 at 4:24 PM, Robert Haas wrote:
>>>> That'
cifically for
cases where there are superuser-only checks at the moment that prevent
GRANT? e.g. pg_show_all_settings for SHOW, pg_show_all_stats for
pg_tablespace_size and friends, pg_stat_statements for, well,
pg_stat_statements and so on? It would be an inferior solution in my
opinion, given that it would de
n pg10, that's acceptable, but it should be a
>>> separate patch.
>>>
>>
>> +1 for not moving the minimum system requirements in the back-branches.
>>
>
> Ok. I reverted this patch in the back-branches, and applied the much less
> invasive "V2
e "commands/user.h"
>> @@ -6677,10 +6678,12 @@ GetConfigOption(const char *name, bool missing_ok,
>> bool restrict_superuser)
>> }
>> if (restrict_superuser &&
>> (record->flags & GUC_SUPERUSER_ONLY) &&
&g
On Wed, Mar 22, 2017 at 3:46 PM, Dave Page wrote:
> On Wed, Mar 22, 2017 at 1:15 PM, Stephen Frost wrote:
>>
>> I did specifically ask for explicit roles to be made to enable such
>> capability and that the pg_monitor role be GRANT'd those roles instead
>> of
's not been done yet.
Yeah, sorry - I missed that for pg_stat_activity. I'll update the patch.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pg
On Wed, Mar 22, 2017 at 12:55 PM, Peter Eisentraut
wrote:
> On 3/22/17 07:48, Dave Page wrote:
>> With the patch, complex monitoring systems can easily be setup with
>> something like:
>>
>> CREATE ROLE monitoring_user LOGIN;
>> GRANT pg_monitor TO monitoring_ro
On Wed, Mar 22, 2017 at 11:32 AM, Robert Haas wrote:
> On Fri, Feb 24, 2017 at 5:14 AM, Dave Page wrote:
>> - Adds a default role called pg_monitor
>> - Gives members of the pg_monitor role full access to:
>> pg_ls_logdir() and pg_ls_waldir()
>> pg
pg_monitor;
> +
> +GRANT pg_read_all_gucs TO pg_monitor;
>
> The new status of this patch is: Waiting on Author
Odd - I get very different rejects than you. Perhaps you didn't apply
my pg_ls_logdir() patch first? In any case, that was committed last
night.
Here's a rebased patch.
T
On Thu, Mar 16, 2017 at 7:05 PM, Robert Haas wrote:
> On Thu, Mar 16, 2017 at 6:09 AM, Dave Page wrote:
>> Hmm, good point. Google seems to be saying there isn't one. Patch
>> updated as you suggest (and I've added back in a function declaration
>> that got l
On Thu, Mar 16, 2017 at 9:54 AM, Thomas Munro
wrote:
> On Thu, Mar 16, 2017 at 10:40 PM, Dave Page wrote:
>>> +const int n = snprintf(NULL, 0, "%lld", attrib.st_size);
>
> I wonder what the portable printf directive is for off_t. Maybe
> better to use
Hi
On Wed, Mar 15, 2017 at 5:27 PM, Robert Haas wrote:
> On Mon, Feb 20, 2017 at 6:21 AM, Dave Page wrote:
>> Patch includes the code and doc updates.
>
> Review:
>
> +strftime(mtime, 25, "%Y-%m-%d %H:%M:%S %Z",
> localtime(&(attrib.st_ctime)));
>
+HP+vQ1LtrgbsYQ=cshzzbqyft5joy...@mail.gmail.com).
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
diff --git a/contrib/pg_buffercache/Makefile b/contrib/pg_buffercache/Makefile
index 497dbeb229
eded.
Using a scheme like that would also mean that the user is more likely
to need to manually update the role their monitoring system uses
following an upgrade.
> - Do not create our own pg_monitor but instead provide
> documentation/scripts for users to create their
Hi
On Tue, Feb 21, 2017 at 5:40 PM, Masahiko Sawada wrote:
> On Mon, Feb 20, 2017 at 8:48 PM, Dave Page wrote:
>> Further to the patch I just submitted
>> (https://www.postgresql.org/message-id/CA%2BOCxow-X%3DD2fWdKy%2BHP%2BvQ1LtrgbsYQ%3DCshzZBqyFT5jOYrFw%40mail.gmail.com)
and restore backups.
Comments?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
has a hard-coded superuser check, but have ACLs that
prevent public execution by default.
Patch includes the code and doc updates.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
diff --git a/doc/src
mailing lists for comments or suggested
changes. If you have comments, please email them to
coc-comme...@postgresql.org no later than 2017-03-05, 11:59PM GMT for
the committee to review.
Regards, Dave.
--
Dave Page
PostgreSQL Core Team
http://www.postgresql.org/
--
Sent via pgsql-hackers mailing
> On 27 Jan 2017, at 17:39, Stephen Frost wrote:
>
> Greetings,
>
> * Simon Riggs (si...@2ndquadrant.com) wrote:
>>> On 27 January 2017 at 14:09, Dave Page wrote:
>>>> On Fri, Jan 27, 2017 at 1:18 PM, Simon Riggs wrote:
>>>>
>>>&
On Fri, Jan 27, 2017 at 1:18 PM, Simon Riggs wrote:
> On 27 January 2017 at 12:56, Dave Page wrote:
>
>> Probably the most common complaint I get from users
>> regarding the management & monitoring tools I work on is that they
>> have to use superuser accounts to g
ms like official advice, yet is
> potentially unsafe: "access can be given to other users via GRANT".
>
> 4. Later, work towards a patch. We have some weeks to get this right.
>
> I'm willing to spend time on workshopping this in Brussels, with any
> attendees.
I
ent & monitoring tools I work on is that they
have to use superuser accounts to get the full benefits, unlike other
DBMSs where you can create a role with just the required privileges
(or indeed, other DBMSs that ship with such roles pre-defined for
convenience).
--
Dave Page
Blog: http://pgs
he system now, because of how successful it has proved
> to be.
Right - we go out of our way to ensure we don't break URLs. That's why
anoncvs.postgresql.org is still actively maintained for example.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB U
On Fri, Sep 9, 2016 at 2:27 PM, Tom Lane wrote:
> Dave Page writes:
>> We needed a specific version that was newer than that shipped with
>> RHEL 6 (or in EPEL) iirc.
>
> Sure hope that's not true of the currently-proposed patch :-(
Looking back at my old emails, ap
by OS, like we do
> for tzdata.
>
> (That said, just checked EDB's ICU support. We currently ship our own libicu
> there, as a part of EPAS, but I don't know the reasoning/history behind
> there.)
We needed a specific version that was newer than that shipped with
RHEL 6
ere is an issue with the Windows x64 build with the version of VC++
that's used for the installers. I believe there was a fix committed
for this yesterday by Tom.
The button was supposed to be removed until we get an updated build -
apologies for the inconvenience.
--
Dave Page
Blog: http://pgs
> On 13 May 2016, at 17:24, Magnus Hagander wrote:
>
>> On Fri, May 13, 2016 at 5:29 PM, Dave Page wrote:
>> On Fri, May 13, 2016 at 4:23 PM, Thom Brown wrote:
>> >
>> > Well, one potential issues is that there may be projects which have
>> > al
On Fri, May 13, 2016 at 5:08 PM, Bruce Momjian wrote:
> On Fri, May 13, 2016 at 12:05:34PM -0400, Stephen Frost wrote:
>> * Dave Page (dp...@pgadmin.org) wrote:
>> > I imagine the bigger issue will be apps that have been written
>> > assuming the first part of the vers
tered all over pgAdmin 3 for
example) - largely because in such apps we're almost always checking
for a version greater than or less than x.y.
I imagine the bigger issue will be apps that have been written
assuming the first part of the version number is only a single digit.
--
D
und: C:\pgbuild\pgadmin3-jinfroster\pgAdmin3.xml.
> C:\pgbuild\pgadmin3-jinfroster\pgAdmin3.targets 45 6 pgAdmin3
Visual Studio seems to delete that file when doing a clean, for
reasons I never quite figured out. You can just check it out from the
git repo again and it should be OK.
t; PgAdmin3 using build-wxmsw.bat.
>
>
> If I remember it right for PgAdminIII needed mingw now.
> Thanks.
pgAdmin III has never supported Mingw, it's always used VC++.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
That would get rid of a lot of logspam.
>
> Would that make sense?
Absolutely. It would be very nice to get rid of such noise.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via
Per discussion at the Brussels developer meeting and within the
release team, the high level schedule for 9.6 will be:
Beta: May (before PGCon)
Release: September
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise
ort" is also entitled to
use either our 9.4 or 9.5 versions which do have JSONB support. Our
new versions are typically released within a couple of months of
PostgreSQL, and in the case of 9.5, the gap was more like 3 weeks.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @p
tgresql.org) as an embedded
database in some applications, and for development/test. There are a
huge number of Windows PostgreSQL users out there.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Comp
On Wed, Dec 2, 2015 at 1:06 PM, Bruce Momjian wrote:
> On Wed, Dec 2, 2015 at 08:53:07AM +0000, Dave Page wrote:
>> On Tue, Dec 1, 2015 at 9:55 PM, Bruce Momjian wrote:
>> > On Tue, Dec 1, 2015 at 06:40:09PM -0300, Alvaro Herrera wrote:
>> >> Bruce Momjian wrote:
able to ensure the same binaries
would run on all the different supported versions.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.
> On 2 Oct 2015, at 17:28, Joshua D. Drake wrote:
>
> Hello,
>
> I believe it is pretty obvious we are moving in the direction of having a
> tracker at this point. The problem is exactly which direction. Stephen has
> offered some resources for his ideas and now I am offering some resources
everyone else has and which somebody has taken the time
> to implement (thus, obviously it has value for them) and which has
> been discussed to general approval at PGCon developer meetings and
> which has been endorsed on this thread by three committers is somehow
> something that nobod
gested, and on the odd occasion when they can't for some reason, we
(core and packagers) figure out the best date for everyone involved.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent
t; newly-created group. But I believe that change is needed.
Timing *decisions* are not made by -core, as I've told you in the
past. They are made by the packagers who do the actual work, based on
suggestions from -core.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
Enterpr
On Fri, May 29, 2015 at 9:55 AM, Pavel Stehule wrote:
>
>
> 2015-05-29 10:37 GMT+02:00 Dave Page :
>>
>> On Fri, May 29, 2015 at 7:27 AM, Pavel Stehule
>> wrote:
>> >
>> >
>> > 2015-05-29 8:20 GMT+02:00 Guillaume Lelarge :
>> >
;> > and older
>>
>> Really, I use Win 2k8 stuff and Win7 quite a lot.
>
>
> On Win 7 you have to search and install now unsupported VS EE 2010.
I've been running 2013 on Windows 7 since it came out. Works perfectly
well, and didn't require any unusual i
On Fri, May 29, 2015 at 9:35 AM, Dave Page wrote:
> On Fri, May 29, 2015 at 7:20 AM, Guillaume Lelarge
> wrote:
>> Le 29 mai 2015 8:10 AM, "Pavel Stehule" a écrit :
>>>
>>> Hi
>>>
>>> I am not sure if PGXN can substitute contrib - ma
allation other extension from EDB stack is difficult,
> unclean, and nothing what I would to use as new base.
The five or six mouse clicks required to install something like Slony
or PostGIS (or both at once) is difficult and unclean?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnak
ready go way further than any
> Linux packages.
The only extra extension we ship is pl/debugger.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgs
/usr/include/sys/vnode.h:105: error: syntax error before "kstat_named_t"
>
> I'd noticed this one as well. This sounds like a installation problem,
> not really ours. Dave, any chance you could look into this, or give
> somebody an account to test what's up?
I
I must fix bug .
>>> after I want run pgadmin4.py, I must fix gravatar import line.
>>
>> --
>> Bruce Momjian http://momjian.us
>> EnterpriseDB http://enterprisedb.com
>>
>> + Everyone has their own god. +
>
>
> timeout :=> '1h');
> pg_drop_scheduled_command('delete obsolete data');
>
> select * from pg_scheduled_commands;
>
>
> Comments, notices?
It's not integrated with the server (though it is integrated with
pgAdmin), but pgAgent provides scheduling serv
have been advised in
the past (by those with appropriate letters after their names) to stop
using the Artistic licence. This is why I spent nearly a year working
on changing pgAdmin to the PostgreSQL licence.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http:
t; than the one used to create the index, and stop using the index until it is
> rebuilt.
>
>
> I'll take a shot at the MINIMUM TODO as outlined above.
>
>
We've already included ICU support in our Postgres Plus Advanced Server
product. Before you spend too much time on th
On Wed, Nov 26, 2014 at 10:13 AM, Jakob Egger wrote:
> Am 26.11.2014 um 11:05 schrieb Dave Page :
>
> You may want to bear in mind that postgres.app is on the main PG
> downloads page on the website. If you're patching Postgres to add a
> feature like this, it would become a
ostgres to add a
feature like this, it would become a fork and would have to be moved
out of the "PostgreSQL Core Distribution" section of the download area
as we only include "pure" distributions there.
--
Dave Page
PostgreSQL Core Team
http://www.postgresql.org/
--
Sent via
postgresql from scratch, ran make check,
> but no pop-up.
>
> I'm on Yosemite. Maybe this was changed.
I've never seen it on any version of OS X (I've worked my way from
Panther to Yosemite). There must be more to it...
--
Dave Page
Blog: http://pgsnake.blogspot.com
lease of MinGW/Msys which is far more
likely to be similar to what someone would want to use at present.
Does anyone really think there's a good reason to keep maintaining
such an obsolete animal?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http:/
s.
That seems like a reasonable approach. I can imagine other uses for a
BACKUP role in the future.
> Do we want redaction in PostgreSQL?
+1
> Do we want it generalised into output format functions?
+1
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK:
On Tue, Sep 23, 2014 at 4:19 PM, Robert Haas wrote:
> On Tue, Sep 23, 2014 at 11:16 AM, Dave Page wrote:
>> Regardless of what Robert may feel, review should only generally be
>> *expected* during a commitfest, but it can be done at any time.
>> Committers are free to co
On Tue, Sep 23, 2014 at 2:00 PM, Andres Freund wrote:
> On 2014-09-23 13:23:32 +0100, Dave Page wrote:
>> Just to be clear here, the *only* issue we should even be discussing
>> is whether the patch should or should not have been committed in the
>> face of those objecti
y
are there as a backstop to make sure that regardless of what the
committers are doing day to day, patch authors know that their patch
is expected to receive some review within N weeks.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
On Sat, Aug 30, 2014 at 11:32 PM, Noah Misch wrote:
> On Tue, Aug 26, 2014 at 10:17:05AM +0100, Dave Page wrote:
>> On Tue, Aug 26, 2014 at 1:46 AM, Tom Lane wrote:
>> > For the last month or so, these two buildfarm animals (which I believe are
>> > the same
th.
However, that would have only affected castoroides, and not
protosciurus which runs under a different environment config. I have
no idea what is causing the current issue - the machine is stable
software-wise, and only has private builds of dependency libraries
update periodically (which are n
ntentional change or not as I wasn't
involved in writing that patch, but I can say that EDB will not be
supporting Windows XP for our future builds now that it's been
(finally) made obsolete by Microsoft when extended support ended in
April.
--
Dave Page
Blog: http://pgsnake.blogspo
On Sat, May 3, 2014 at 8:29 PM, Andres Freund wrote:
> On 2014-05-03 13:25:32 -0400, Tom Lane wrote:
>> Andres Freund writes:
>> > On 2012-09-17 08:23:01 -0400, Dave Page wrote:
>> >> I've added MAX_CONNECTIONS=5 to both Castoroides and Protosciurus.
>&g
t; Andres Freund http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
--
Dave Page
Chief Architect, Tools & Installers
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.b
> On 2 Mar 2014, at 05:20, Noah Misch wrote:
>
>> On Sat, Mar 01, 2014 at 05:51:46PM -0500, Andrew Dunstan wrote:
>>> On 03/01/2014 05:10 PM, Tom Lane wrote:
>>> One other thought here: is it actually reasonable to expend a lot of effort
>>> on the Windows case? I'm not aware that people norma
On Mon, Feb 17, 2014 at 2:58 PM, Tom Lane wrote:
> Dave Page writes:
>> On Fri, Feb 14, 2014 at 5:32 PM, Tom Lane wrote:
>>> (BTW, narwhal is evidently not trying to build plpython. I wonder
>>> why not?)
>
>> Not sure - it's certainly installed on the
is evidently not trying to build plpython. I wonder
> why not?)
Not sure - it's certainly installed on the box. I've enabled it for
now, and will see what happens.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Ent
On Sun, Feb 2, 2014 at 3:59 PM, Tom Lane wrote:
> Dave Page writes:
>> On Sun, Feb 2, 2014 at 1:03 AM, Tom Lane wrote:
>>> I think we should give serious consideration to desupporting this
>>> combination so that we can get rid of the plague of PGDLLIMPORT
>&g
builds.
I'm happy to replace it with something newer as time allows - what do
we consider to be the biggest gap? I have an MSDN subscription, so can
do any versions of Windows or VC++ (and obviously Mingw).
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
Enterprise
I couldn't agree more. Whatever we do here we need a standard
mechanism that tool developers can expect to be present and the same
on all servers. Otherwise, we make it extremely difficult to build
tools like pgAdmin, check_postgres.pl and so on.
--
Dave Page
Blog: http://pgsnake.blogspot.co
enaming krb5 would be just that the build
> would proceed without it. From memory I don't thing the config settings are
> sanity checked.
Yeah, sorry - we had an aircon failure where my animals live, so
they've been down for a couple of weeks. We've got a complete new
sy
ng that users
could disable NLS in their extension to avoid issues with the missing
header, but that's not a good solution.
> On Mon, Jan 6, 2014 at 2:44 PM, Dave Page wrote:
>>
>> On Mon, Jan 6, 2014 at 3:32 AM, Craig Ringer
>> wrote:
>> > Hi all
>> &
rant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
--
Dave Page
Blog: http://pgsnak
; as PostgreSQL Service creates a postgres
>> > process using an absolute path which indicates the
>> > location of "postgres.exe",but the path is not enclosed
>> > in quotation.
>> >
>> > Therefore,if the above-mentio
Just a quick heads-up: following discussion within the core team and
the packagers, we're planning to wrap tarballs for 8.4 - 9.3
backbranch releases on Monday 7th October for release
on Thursday 10th.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK:
On Mon, Aug 19, 2013 at 10:21 AM, Dimitri Fontaine
wrote:
> Dave Page writes:
>> The escalation happens because in a normal system-wide installation of
>> PostgreSQL as you'd see on most production systems will have the
>> installation directories and binaries own
he change suggested, but I feel pretty
strongly that it should not be allowed in a default configuration, and
should be something that can be disabled from outside of
postgresql.conf (which of course, can often be modified through
PostgreSQL by a superuser - and yes, I realise there is ris
ersion info. That has proven to be extremely useful in the
past, particularly during QA where people may be testing snapshot
builds.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pg
similar would do quite nicely.
It's already sitting behind Varnish, but the vast majority of pages on
that site would only ever be hit by crawlers anyway, so I doubt that'd
help a great deal as those pages would likely expire from the cache
before it really saved us anything.
--
Dave Pa
s. I realise it doesn't help these users
(who doubtless don't know it exists) but what we do these days is drop
a "pg_env.sh" file in the installation directory that the user can
source to set their PATH and various PG* environment variables when
they need/want to.
--
Dav
proach: Linux Kernel, Drizzle, etc.
> There's some legal advantages, as well as disadvantages, in having the
> copyright rest with the original contributors. Mostly, it prevents
> relicensing of the whole project.
No it doesn't - it just makes it a pain in the arse (I know, I&#x
On Mon, Jun 3, 2013 at 3:59 PM, Kevin Grittner wrote:
> Dave Page wrote:
>> Kevin Grittner wrote:
>>> Dave Page wrote:
>
>>>> In playing with materialized views, I noticed that they still
>>>> seem to have an _RETURN rule implicitly created like a
in the future.
> On Mon, Jun 3, 2013 at 6:58 AM, Dave Page wrote:
>>
>> Hi
>>
>> In playing with materialized views, I noticed that they still seem to
>> have an _RETURN rule implicitly created like a regular view. This
>> doesn't seem right to me - is
1 - 100 of 1719 matches
Mail list logo
