> 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
On Thu, Aug 17, 2017 at 2:58 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> Dave Page <dp...@postgresql.org> 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
P_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/
re?
>
Well crake is a Fedora box - and we have no problems on Linux, only on
Windows.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Thu, May 4, 2017 at 3:54 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> Alvaro Herrera <alvhe...@2ndquadrant.com> writes:
> > Something like the (untested) attached perhaps?
>
> Looks plausible, I'm not in a position to test though.
Sandeep/Paresh - can you test please
sql.
org/gitweb/?p=postgresql.git;a=commit;h=eaba54c20c5ab2cb6aaffa57fd
4990dfe2c7
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Thu, Mar 30, 2017 at 2:24 PM, Simon Riggs <si...@2ndquadrant.com> wrote:
> On 30 March 2017 at 18:29, Simon Riggs <si...@2ndquadrant.com> wrote:
>
>> Moving to commit this over the next hour. Last chance...
>
> Done. Great work Dave, thanks everybody.
Thanks Si
cute 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 Comp
ous
>> ones, so it seems reasonable to give more time. We have a large number
>> of patches still waiting for review.
>
> +1
+1
--
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
Hi
On Tue, Mar 28, 2017 at 2:22 PM, Stephen Frost <sfr...@snowman.net> 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 g
On Tue, Mar 28, 2017 at 1:52 PM, Mark Dilger <hornschnor...@gmail.com> wrote:
>
>> On Mar 28, 2017, at 9:55 AM, Robert Haas <robertmh...@gmail.com> wrote:
>>
>> On Tue, Mar 28, 2017 at 12:47 PM, Dave Page <dp...@pgadmin.org> wrote:
>>>> I don't s
?
Thanks!
On Tue, Mar 28, 2017 at 1:37 PM, Stephen Frost <sfr...@snowman.net> wrote:
> Greetings,
>
> * Robert Haas (robertmh...@gmail.com) wrote:
>> On Tue, Mar 28, 2017 at 12:47 PM, Dave Page <dp...@pgadmin.org> wrote:
>> >> I don't see any precedent in the
On Tue, Mar 28, 2017 at 12:55 PM, Robert Haas <robertmh...@gmail.com> wrote:
> On Tue, Mar 28, 2017 at 12:47 PM, Dave Page <dp...@pgadmin.org> wrote:
>>> I don't see any precedent in the code for having a hardcoded role, other
>>> than
>>> superuser, an
On Tue, Mar 28, 2017 at 12:04 PM, Mark Dilger <hornschnor...@gmail.com> wrote:
>
>> On Mar 28, 2017, at 8:34 AM, Dave Page <dp...@pgadmin.org> wrote:
>>
>> On Tue, Mar 28, 2017 at 11:31 AM, Peter Eisentraut
>> <peter.eisentr...@2ndquadrant.com> wro
On Tue, Mar 28, 2017 at 11:39 AM, Peter Eisentraut
<peter.eisentr...@2ndquadrant.com> wrote:
> On 3/28/17 11:34, Dave Page wrote:
>> On Tue, Mar 28, 2017 at 11:31 AM, Peter Eisentraut
>> <peter.eisentr...@2ndquadrant.com> wrote:
>>> This patch touches th
d
some files, but that was fixed within an hour 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
On Mon, Mar 27, 2017 at 3:51 AM, Simon Riggs <si...@2ndquadrant.com> wrote:
> On 25 March 2017 at 16:30, Dave Page <dp...@pgadmin.org> wrote:
>
>> I believe this and other reasons we've described are exactly why other DBMS'
>> do what we're proposing.
>
> It
Hi
> On 25 Mar 2017, at 15:55, Stephen Frost <sfr...@snowman.net> wrote:
>
> Robert,
>
> * Robert Haas (robertmh...@gmail.com) wrote:
>>> On Fri, Mar 24, 2017 at 12:46 PM, Dave Page <dp...@pgadmin.org> wrote:
>>>> On Fri, Mar 24, 2017 at 4:
ally 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
and applied the much less
> invasive "V2" patch [1] instead. HEAD is unchanged, so narwhal still fails
> there.
>
> Dave: the consensus is that we no longer support the old version of MinGW
> that narwhal is using, for PostgreSQL v 10. Can you modify the
> configuration of narwhal to not try building 'master' anymore, or upgrade
> the toolchain, please?
>
I've disabled it. Thanks.
--
Dave Page
PostgreSQL Core Team
http://www.postgresql.org/
+6678,12 @@ GetConfigOption(const char *name, bool missing_ok,
>> bool restrict_superuser)
>> }
>> if (restrict_superuser &&
>> (record->flags & GUC_SUPERUSER_ONLY) &&
>> - !superuser())
>>
On Wed, Mar 22, 2017 at 3:46 PM, Dave Page <dp...@pgadmin.org> wrote:
> On Wed, Mar 22, 2017 at 1:15 PM, Stephen Frost <sfr...@snowman.net> wrote:
>>
>> I did specifically ask for explicit roles to be made to enable such
>> capability and that the pg_monitor ro
eems like
> that'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 mailin
On Wed, Mar 22, 2017 at 12:55 PM, Peter Eisentraut
<peter.eisentr...@2ndquadrant.com> 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 monitorin
On Wed, Mar 22, 2017 at 11:32 AM, Robert Haas <robertmh...@gmail.com> wrote:
> On Fri, Feb 24, 2017 at 5:14 AM, Dave Page <dp...@pgadmin.org> wrote:
>> - Adds a default role called pg_monitor
>> - Gives members of the pg_monitor role full access to:
>>
FUNCTION pg_ls_waldir() TO 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
nigh
On Thu, Mar 16, 2017 at 7:05 PM, Robert Haas <robertmh...@gmail.com> wrote:
> On Thu, Mar 16, 2017 at 6:09 AM, Dave Page <dp...@pgadmin.org> wrote:
>> Hmm, good point. Google seems to be saying there isn't one. Patch
>> updated as you suggest (and I've added bac
On Thu, Mar 16, 2017 at 9:54 AM, Thomas Munro
<thomas.mu...@enterprisedb.com> wrote:
> On Thu, Mar 16, 2017 at 10:40 PM, Dave Page <dp...@pgadmin.org> wrote:
>>> +const int n = snprintf(NULL, 0, "%lld", attrib.st_size);
>
> I wonder what the portab
Hi
On Wed, Mar 15, 2017 at 5:27 PM, Robert Haas <robertmh...@gmail.com> wrote:
> On Mon, Feb 20, 2017 at 6:21 AM, Dave Page <dp...@pgadmin.org> wrote:
>> Patch includes the code and doc updates.
>
> Review:
>
> +strftime(mtime, 25, "%Y-%m-%d %H:%M
+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
ade.
> - Do not create our own pg_monitor but instead provide
> documentation/scripts for users to create their own "monitor" roles.
The whole point here is to minimise the requirements on the user, and
have a good set of default roles.
> It seems at least unlikely that we'l
Hi
On Tue, Feb 21, 2017 at 5:40 PM, Masahiko Sawada <sawada.m...@gmail.com> wrote:
> On Mon, Feb 20, 2017 at 8:48 PM, Dave Page <dp...@pgadmin.org> wrote:
>> Further to the patch I just submitted
>> (https://www.postgresql.org/message-id/CA%2BOCxow-X%3
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
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/sgml
the 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 <sfr...@snowman.net> wrote:
>
> Greetings,
>
> * Simon Riggs (si...@2ndquadrant.com) wrote:
>>> On 27 January 2017 at 14:09, Dave Page <dp...@pgadmin.org> wrote:
>>>> On Fri, Jan 27, 2017 at 1:
On Fri, Jan 27, 2017 at 1:18 PM, Simon Riggs <si...@2ndquadrant.com> wrote:
> On 27 January 2017 at 12:56, Dave Page <dp...@pgadmin.org> wrote:
>
>> Probably the most common complaint I get from users
>> regarding the management & monitoring tools I work on is
when they
> follow the next part which seems 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
ement & 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://pg
this day. We're far
> too invested in the 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
Twit
On Fri, Sep 9, 2016 at 2:27 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> Dave Page <dp...@pgadmin.org> 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
the libuci supplied 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 (
ng/pgdownload#windows
There 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.
--
> On 13 May 2016, at 17:24, Magnus Hagander <mag...@hagander.net> wrote:
>
>> On Fri, May 13, 2016 at 5:29 PM, Dave Page <dp...@pgadmin.org> wrote:
>> On Fri, May 13, 2016 at 4:23 PM, Thom Brown <t...@linux.com> wrote:
>> >
>> > Well, on
On Fri, May 13, 2016 at 5:08 PM, Bruce Momjian <br...@momjian.us> 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
released as 8.0 - but is smattered 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.
--
> task. File not found: 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
hassle on
>> building
>> 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
quot;).
>
> 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 Co
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
't have all the cool/modern jsonb support" 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://pgs
uently downloaded build from EDB or postgresql.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 Pos
rwise we wouldn't be 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-hac
On Wed, Dec 2, 2015 at 1:06 PM, Bruce Momjian <br...@momjian.us> 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 <br...@momjian.us> wrote:
>> > On Tue, Dec 1, 2015 at 06:40:09PM -0300, Alvaro Herr
> 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
dding ourselves that a
> feature that 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 committ
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 via pgsql-hackers mailing list (pgsql
required to install something like Slony
or PostGIS (or both at once) is difficult and unclean?
--
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
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 installation.
--
Dave Page
Blog: http://pgsnake.blogspot.com
On Fri, May 29, 2015 at 9:35 AM, Dave Page dp...@pgadmin.org wrote:
On Fri, May 29, 2015 at 7:20 AM, Guillaume Lelarge
guilla...@lelarge.info wrote:
Le 29 mai 2015 8:10 AM, Pavel Stehule pavel.steh...@gmail.com a écrit :
Hi
I am not sure if PGXN can substitute contrib - mainly due
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 (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
On Fri, May 29, 2015 at 9:55 AM, Pavel Stehule pavel.steh...@gmail.com wrote:
2015-05-29 10:37 GMT+02:00 Dave Page dp...@pgadmin.org:
On Fri, May 29, 2015 at 7:27 AM, Pavel Stehule pavel.steh...@gmail.com
wrote:
2015-05-29 8:20 GMT+02:00 Guillaume Lelarge guilla...@lelarge.info:
Le
, any chance you could look into this, or give
somebody an account to test what's up?
I'm not going to be able to look at this, at least this week. I can
give someone on the EDB team access - Robert; can one of your guys
take a look?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
ALAN
http://sckn.org
--
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
pg_scheduled_commands;
Comments, notices?
It's not integrated with the server (though it is integrated with
pgAdmin), but pgAgent provides scheduling services for PostgreSQL
already, offering multi-schedule, multi-step job execution.
http://www.pgadmin.org/docs/1.20/pgagent.html
--
Dave Page
Blog
. 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://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers
contributed back. The people I need to speak to
are OOO for Thanksgiving at the moment though, so it may be a few days.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
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 pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
On Wed, Nov 26, 2014 at 10:13 AM, Jakob Egger ja...@eggerapps.at wrote:
Am 26.11.2014 um 11:05 schrieb Dave Page dp...@postgresql.org:
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
-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
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise
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://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql
review within N weeks.
--
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
On Tue, Sep 23, 2014 at 2:00 PM, Andres Freund and...@anarazel.de 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 objections. As Josh
On Tue, Sep 23, 2014 at 4:19 PM, Robert Haas robertmh...@gmail.com wrote:
On Tue, Sep 23, 2014 at 11:16 AM, Dave Page dp...@pgadmin.org 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
On Sat, Aug 30, 2014 at 11:32 PM, Noah Misch n...@leadboat.com 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 t...@sss.pgh.pa.us wrote:
For the last month or so, these two buildfarm animals (which I believe are
the same physical
, and only has private builds of dependency libraries
update periodically (which are not used for the buildfarm). If I had
to hazard a guess, I'd suggest this is an early symptom of an old
machine which is starting to give up.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB
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.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise
On Sat, May 3, 2014 at 8:29 PM, Andres Freund and...@2ndquadrant.com wrote:
On 2014-05-03 13:25:32 -0400, Tom Lane wrote:
Andres Freund and...@2ndquadrant.com writes:
On 2012-09-17 08:23:01 -0400, Dave Page wrote:
I've added MAX_CONNECTIONS=5 to both Castoroides and Protosciurus.
I've
--
Dave Page
Chief Architect, Tools Installers
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
On 2 Mar 2014, at 05:20, Noah Misch n...@leadboat.com 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
it for
now, and will see what happens.
--
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
On Mon, Feb 17, 2014 at 2:58 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Dave Page dp...@pgadmin.org writes:
On Fri, Feb 14, 2014 at 5:32 PM, Tom Lane t...@sss.pgh.pa.us wrote:
(BTW, narwhal is evidently not trying to build plpython. I wonder
why not?)
Not sure - it's certainly installed
On Sun, Feb 2, 2014 at 3:59 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Dave Page dp...@pgadmin.org writes:
On Sun, Feb 2, 2014 at 1:03 AM, Tom Lane t...@sss.pgh.pa.us wrote:
I think we should give serious consideration to desupporting this
combination so that we can get rid of the plague
an MSDN subscription, so can
do any versions of Windows or VC++ (and obviously Mingw).
--
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 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.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via
bring everything up again tomorrow (I'm out of
town for a couple of days).
--
Dave Page
PostgreSQL Core Team
http://www.postgresql.org/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
--
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
was suggesting 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 dp...@pgadmin.org wrote:
On Mon, Jan 6, 2014 at 3:32 AM, Craig Ringer cr...@2ndquadrant.com
wrote:
Hi all
Out
≫
・区分:秘密
・開示:必要最小限で可
・持出:禁止
・期限:無期限
・用済後:廃棄
--
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
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: http
to that).
--
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
On Mon, Aug 19, 2013 at 10:21 AM, Dimitri Fontaine
dimi...@2ndquadrant.fr wrote:
Dave Page dp...@pgadmin.org 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
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 pgsql-hackers mailing list (pgsql-hackers@postgresql.org
pages would likely expire from the cache
before it really saved us anything.
--
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
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.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter
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've done it).
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http
, +
pg_class.relacl, +
pg_class.reloptions+
FROM pg_class;
(1 row)
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
time in the future.
On Mon, Jun 3, 2013 at 6:58 AM, Dave Page dp...@pgadmin.org 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 there a reason?
viper:~ dpage$ /usr
On Mon, Jun 3, 2013 at 3:59 PM, Kevin Grittner kgri...@ymail.com wrote:
Dave Page dp...@pgadmin.org wrote:
Kevin Grittner kevin.gritt...@enterprisedb.com wrote:
Dave Page dp...@pgadmin.org wrote:
In playing with materialized views, I noticed that they still
seem to have an _RETURN rule
On Fri, May 10, 2013 at 2:47 AM, Peter Eisentraut pete...@gmx.net wrote:
On Thu, 2013-05-09 at 10:11 -0400, Peter Eisentraut wrote:
On 5/9/13 3:25 AM, Dave Page wrote:
BTW - it's always worked fine for us on 64 bit machines with the past
few major releases of both PG and Python - are you
1 - 100 of 1699 matches
Mail list logo