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
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
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.
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
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
> 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
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
#.2Fcontrib.2Fpg_upgrade
>>
>> The problem is that the "Contents" menu on the top right of the page
>> doesn't allow a clickable link to that section, and many others.
>
> It does for me...
Doesn't here. FYI, neither do others such as 2.6, 2.7, 6.1 &a
ry much in sight on my calendar :-)
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
t we have bumped the catversion? The installers can't tell
that beta1 clusters won't work with beta2 :-(
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Fri, Jun 4, 2010 at 2:49 PM, Tom Lane wrote:
> Bruce Momjian writes:
>> Dave Page wrote:
>>> Shouldn't we have bumped the catversion? The installers can't tell
>>> that beta1 clusters won't work with beta2 :-(
>
>> That is an interesting po
On Fri, Jun 4, 2010 at 4:30 PM, Tom Lane wrote:
> Dave Page writes:
>> On Fri, Jun 4, 2010 at 2:49 PM, Tom Lane wrote:
>>> Right, because the catalog contents didn't change. Seems to me you'd
>>> better teach the installers to look at PG_CONTROL_VERSION
On Fri, Jun 4, 2010 at 7:30 PM, Tom Lane wrote:
> Dave Page writes:
>> On Fri, Jun 4, 2010 at 4:30 PM, Tom Lane wrote:
>>> XLOG_PAGE_MAGIC --- bump on incompatible change in WAL contents
>
>> How can I get that from an existing data directory? I don't see it in
But you can go for "pixin" or "pigskin" if you'd
>> rather. ;-)
>>
>> My bike shed is chartreuse,
>
> heh I'm with Robert on that PGXN just sounds and speels weird - PGAN was
> much easier ;)
+1
--
Dave Page
EnterpriseDB UK: http://w
nges, of course.
>
> #1 is most likely the easiest one.
+1 for #1. Changing history and the resulting possibility of becoming
one's own grandfather always makes me nervous.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql
that claim to be CVS version x.y.z, but actually are
> different from that, because of back-patching activity after the git
> transition. That seems like a recipe for huge confusion in itself.
Agreed. They should be removed from the active back branches.
--
Dave Page
EnterpriseDB UK: http:/
en to ensure
it works :-)
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Tue, Jul 13, 2010 at 4:48 PM, Thom Brown wrote:
> On 13 July 2010 16:44, Thom Brown wrote:
>> On 13 July 2010 16:31, Dave Page wrote:
>>> We had a report of the above error from a pgAdmin user testing
>>> 1.12.0b3 with PG 9.0b3. The (highly simplified) quer
olve the column based on whether you're a superuser or not,
just because it's not qualified?
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscrip
27;2', col2b = '113', col3 = 'foo', col4
= '42' WHERE id = '2'
! (1 row)
!
SELECT dblink_build_sql_delete('test_dropped', '2', 1,
ARRAY['2'::TEXT]);
! dblink_build_sql_delete
! --
On Tue, Jul 20, 2010 at 4:53 PM, Robert Haas wrote:
> On Tue, Jul 20, 2010 at 11:08 AM, Dave Page wrote:
>> Any ideas?
>
> Are you by any chance running off of the broken git mirror?
>
> http://archives.postgresql.org/pgsql-hackers/2010-07/msg00916.php
I might be, ye
possible until Guillaume did so on his
first commit to the new pgAdmin GIT repo. It seems to work nicely:
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commit;h=08e2826d90129bd4e4b3b7462bab682dd6a703e4
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
On Wed, Jul 21, 2010 at 5:54 PM, Robert Haas wrote:
> We need to decide what email addresses committers will use on the new
> git repository when they commit.
Are you are aware that we already have a list of "approved" addresses
for the committers?
--
Dave Page
Enter
On Thu, Jul 22, 2010 at 9:11 AM, Magnus Hagander wrote:
> On Thu, Jul 22, 2010 at 10:04, Dave Page wrote:
>> On Wed, Jul 21, 2010 at 5:54 PM, Robert Haas wrote:
>>> We need to decide what email addresses committers will use on the new
>>> git repository when they comm
tached patch adds two additional functions to
> contrib/sslinfo to report this information.
>
> Any objections to me committing this?
Might wanna fix this first:
+PG_FUNCTION_INFO_V1(ssl_veresion);
^^^^
--
Dave Page
EnterpriseDB UK: http:
it is making pgAdmin look bad. Dave, is there a hack you can add to
> pgAdmin to work around the join issue until we can fix the backend?
It wouldn't make much difference if there was - the majority of people
won't get it until they upgrade their server anyway.
--
Dave P
On Fri, Jul 30, 2010 at 12:17 AM, Tom Lane wrote:
> Dave Page writes:
>> We had a report of the above error from a pgAdmin user testing
>> 1.12.0b3 with PG 9.0b3. The (highly simplified) query below works fine
>> as a superuser:
>
>> SELECT pg_get_expr(proarg
to
> or
> pg_ctl register -N "s-name" -S demand
>
> The created service will be SERVICE_AUTO_START or SERVICE_DEMAND_START
> respectively.
Hi,
Please post the patch to the mailing list, and add it to the next
commitfest: https://commitfest.postgresql.org/action
is also valuable for monitoring and system
administration. Both would be ideal :-)
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
;t put yourself down. You're not that old :-p
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscr
ng an initdb
> failure in 8.4 and up ("cache lookup failed for type 0" while processing
> system_views.sql). I'm betting this is some sort of
> over-aggressive-optimization problem, but it's hard to tell much from
> the buildfarm logs. Could you look into tha
On Tue, Aug 31, 2010 at 10:28 AM, Dave Page wrote:
> On Mon, Aug 30, 2010 at 3:50 AM, Tom Lane wrote:
>> Also, although moa is actually green for 8.3, it's showing an initdb
>> failure in 8.4 and up ("cache lookup failed for type 0" while processing
>> sys
eap size, we
fall over.
It shouldn't matter as desktop heap is allocated on a per-session
basis, but are you logging on using the service account to run your
admin tasks Cristian? If so, do you see the problem if you login
interactively using a different account?
--
Dave Page
Blog: http://p
On Tue, Aug 31, 2010 at 2:51 PM, Tom Lane wrote:
> Dave Page writes:
>>> On Mon, Aug 30, 2010 at 3:50 AM, Tom Lane wrote:
>>>> Also, although moa is actually green for 8.3, it's showing an initdb
>>>> failure in 8.4 and up ("cache lookup failed for
On Tue, Aug 31, 2010 at 3:03 PM, Tom Lane wrote:
> Dave Page writes:
>> On Mon, Aug 30, 2010 at 3:50 AM, Tom Lane wrote:
>>> moa, which is claimed on the buildfarm dashboard to be using gcc but is
>>> actually using cc, hits the spinlock problem in 8.0 and 8.1 and th
#x27;s hard to see what would bring the
server down though...
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
On Tue, Aug 31, 2010 at 4:27 PM, Bruce Momjian wrote:
> Dave Page wrote:
>> On Tue, Aug 31, 2010 at 3:40 PM, Cristian Bittel wrote:
>> > To Dave's question, this behavior occurs on all Windows Server interactive
>> > sessions, no matter if Administrators
On Tue, Aug 31, 2010 at 4:35 PM, Bruce Momjian wrote:
> Dave Page wrote:
>> On Tue, Aug 31, 2010 at 4:27 PM, Bruce Momjian wrote:
>> > We have already found that exceeding desktop heap might cause a
>> > CreateProcess to return success but later fail with a return cod
tually something that is important to us - it
forces us to fix obvious issues, and makes it much harder to
inadvertently miss important changes.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sen
hird part
tools, other changes to the catalogs are not, and masking them could
potentially hide bugs or issues that need to be fixed to actually work
properly with the newer version of the server.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://ww
k on x86 is not the hard part.
I believe there's a PPC box in our storage facility in NJ that we
might be able to dig out for you. There's also a couple in our India
office. Let me know if they'd be of help.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @
On Thu, Jul 21, 2011 at 8:25 PM, Robert Haas wrote:
> On Thu, Jul 21, 2011 at 3:22 PM, Dave Page wrote:
>> On Thu, Jul 21, 2011 at 8:15 PM, Robert Haas wrote:
>>> I think the real challenge is going to be testing. If anyone has a
>>> machine with weak memory ordering
th psql.
Yup:
raptor:PEM dpage$ uname -a
Darwin raptor.local 11.0.0 Darwin Kernel Version 11.0.0: Sat Jun 18
12:56:35 PDT 2011; root:xnu-1699.22.73~1/RELEASE_X86_64 x86_64
raptor:PEM dpage$ which psql
/usr/bin/psql
raptor:PEM dpage$ psql --version
psql (PostgreSQL) 9.0.4
contai
On Fri, Jul 22, 2011 at 5:16 PM, Tom Lane wrote:
> Dave Page writes:
>> On Fri, Jul 22, 2011 at 5:01 PM, Peter Geoghegan
>> wrote:
>>> On 22 July 2011 03:24, Tom Lane wrote:
>> I had a bug filed with Apple about that, and today I got some auto-mail
>> indic
be one
> thing. That is true for libssl, and likely zlib, but not here.
>
Also consider if the library is widely available on common distros or
not. If not, packagers are going to have to start packaging that
first, in order to build the PostgreSQL packages. This is a *huge*
issue for use if w
ty is going to be
> absent most of the time anyway.
Yup.
--
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
ld be around I think.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Sat, Jul 30, 2011 at 8:25 PM, Tom Lane wrote:
> I think you had better plan on incorporating GNU readline into installer
> builds for Lion.
Unfortunately the licence makes that a non-starter.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK
er
>> > builds for Lion.
>>
>> Unfortunately the licence makes that a non-starter.
>
> A fixed version of libedit, then?
Yes, that's the best we can do.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Post
On Mon, Aug 1, 2011 at 6:46 PM, David Fetter wrote:
> On Sat, Jul 30, 2011 at 08:32:03PM +0100, Dave Page wrote:
>> On Sat, Jul 30, 2011 at 8:25 PM, Tom Lane wrote:
>> > I think you had better plan on incorporating GNU readline into
>> > installer builds for Lion.
>
On Monday, August 1, 2011, David Fetter wrote:
> On Mon, Aug 01, 2011 at 07:17:00PM +0100, Dave Page wrote:
>> On Mon, Aug 1, 2011 at 6:46 PM, David Fetter wrote:
>> > On Sat, Jul 30, 2011 at 08:32:03PM +0100, Dave Page wrote:
>> >> On Sat, Jul 30, 2011 at 8:25
ions into core, then it seems
reasonable to add more options for password storage to help those who
need to meet mandated standards.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent vi
The current plan (or, the last one I recall) is to push another 9.1
release tomorrow, for Monday release. Are we going with beta4 or rc1?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via
2011/8/17 Devrim GÜNDÜZ :
> On Wed, 2011-08-17 at 14:00 +0100, Dave Page wrote:
>> Are we going with beta4 or rc1?
>
> RC1:
>
> http://archives.postgresql.org/message-id/19869.1312298...@sss.pgh.pa.us
In Tom's final email to the -core thread he mentions I see now that he
On Wed, Aug 17, 2011 at 4:47 PM, Jan Urbański wrote:
> On 17/08/11 15:00, Dave Page wrote:
>> The current plan (or, the last one I recall) is to push another 9.1
>> release tomorrow, for Monday release. Are we going with beta4 or rc1?
>
> Sorry to butt in, but it would probab
On Wed, Aug 17, 2011 at 5:16 PM, Thom Brown wrote:
> On 17 August 2011 16:56, Jan Urbański wrote:
>>
>> On 17/08/11 17:50, Thom Brown wrote:
>> > On 17 August 2011 16:47, Jan Urbański wrote:
>> >
>> >> On 17/08/11 15:00, Dave Page wrote:
>> >
nt to maintain a list of these in
>> the docs.
>
> Wiki page, maybe?
For example this one: http://wiki.postgresql.org/wiki/Foreign_data_wrappers
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Comp
s and could have used some
>> other way to get the code.
>
> Do we have download stats for the alphas? Dave?
Download numbers for the installers were bordering on noise compared to the
GA builds last time I looked, double figures iirc. I don't know about the
tarb
(*) from clickthrus where path like
'%postgresql-9.0.4.tar.%' and ts >= '2009-09-01';
count
---
34769
(1 row)
Note that these are only numbers from people who click through the
flags pages on the website. We don't have numbers for people who
download directly from th
conference audience. In the case of PG Conference
Europe which I suspect you are alluding to there were a significant
number of talks submitted that would be of far more interest and
benefit to our primary audience of end users.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitt
s was responsible for taking care of
> Postgresql - taking care of MySQL others did.
My point remains - Sun were never in a position to say who represents
PostgreSQL.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise
On Fri, Sep 16, 2011 at 8:47 AM, Susanne Ebrecht
wrote:
> On 16.09.2011 14:47, Dave Page wrote:
>>
>> My point remains - Sun were never in a position to say who represents
>> PostgreSQL.
>
> Dave,
>
> the procedure works different. The country representation ask
On Fri, Sep 16, 2011 at 9:49 AM, Susanne Ebrecht
wrote:
> On 16.09.2011 15:59, Dave Page wrote:
>>
>> other plans less than 2 years ago. For me, a representative would have
>> been reporting back to us after each meeting, and discussing points to
>> raise before ea
On Sunday, September 18, 2011, Peter Eisentraut wrote:
> On fre, 2011-09-16 at 08:59 -0500, Dave Page wrote:
>> You're missing my point completely. You say you represent PostgreSQL
>> on the SQL Committee (or German working group, but that's not the
>> point), ye
9.1.1? I'm not sure our QA guys will be able to cope
with verification of so many individual installers in that timeframe -
8.2 - 9.0 is hard enough to do in one go.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enter
storical record of doing updates
>> roughly quarterly. Should we settle that detail now? That is,
>> does "after December" really mean "in or after December", or did we
>> really mean "after"?
>>
>>
>
> If we really want to get that
2011/9/20 Tom Lane :
> Dave Page writes:
>> 2011/9/20 Andrew Dunstan :
>>> On 09/20/2011 10:28 AM, Tom Lane wrote:
>>>> does "after December" really mean "in or after December", or did we
>>>> really mean "after"?
>
>
On Tue, Sep 20, 2011 at 3:57 PM, Tom Lane wrote:
> Dave Page writes:
>> On Tue, Sep 20, 2011 at 12:37 AM, Tom Lane wrote:
>>> As has been mentioned a couple times, we're well overdue for updates of
>>> the back branches. Seems like time to get that done, so we
. Also, at
>> least at some point in the past, a pgfoundry project was easier to
>> manage than getting anything done about a @postgresql.org mailing list.
>
> The document manager might be useful, true. I cannot speak about past
> administrators of the Majordomo installation t
a service on Windows.
--
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
t; make it work as best we can.
>
> I disagree. If people were using it we would have had many more bug
> reports about pg_ctl not working.
Debian/ubuntu packages and our own project infrastructure use it.
Though, there is a non-trivial script wrapping it, presumably to try
to make it work pr
On Tue, Oct 4, 2011 at 7:55 PM, Tom Lane wrote:
> I'm betting not, because I don't see any support for copying their
> values down to child processes in
> write_nondefault_variables/read_nondefault_variables.
Correct, it does not.
--
Dave Page
Blog: http://pgsnake.b
On Tue, Oct 4, 2011 at 8:27 PM, Tom Lane wrote:
> Dave Page writes:
>> On Tue, Oct 4, 2011 at 7:55 PM, Tom Lane wrote:
>>> I'm betting not, because I don't see any support for copying their
>>> values down to child processes in
>>> write_
ouldn't be that much work to fix:
This is in the old 8.2 MSI installer, which doesn't even support
Windows 7 (and would require more work than just this to do so). The
last ever release of 8.2 will happen long before Windows 8 is going to
go GA - it's safe to say this version is never
with uncaring.
It might have appeared to successfully install, but that doesn't mean
it's setup the way we want it. For example, none of the administrative
menu shortcuts in that version will do privilege escalation which is
more or less required in Windows 7+.
--
Dave Page
Blog:
raining/pgdownload>
>
>
No, please use http://www.postgresql.org/download/
That's the stable URL that will always point to our downloads.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
The reported git failures from the buildfarm should clear on the next run -
they're the result of an upgrade to the git package on the git server which
left the git-daemon in an non-functioning state. It's back up now.
Apologies for the noise.
--
Dave Page
Blog: http://pgsnake.bl
/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
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
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
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
;> > 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: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 :
>> >
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
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
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
nce in the real world.
I would disagree with that. Deployments in the cloud may have fast,
but untrustworthy network connections.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hacke
Bruce Momjian wrote:
> Peter Eisentraut wrote:
>> I was hoping that we're deprecating contrib/xml2, so I wouldn't add more
>> features to it.
>
> Author states:
>
>> I understand that XML support is planned and at least partially
>> implemented for 8.3, but many production instances will be unab
Andrew Dunstan wrote:
So, before an investment of any more time is made by either Abhijit or
myself, I would like to get confirmation that a) there is broad
agreement on the desirability of the feature
Yes, absolutely desirable.
and b) that there is broad
agreement on the general design (
Andrew Dunstan wrote:
>
> No loss, but, per previous discussion, it would block and try to get
> other backends to collect their outstanding notifications.
>
> Let's say we provide 100Kb for this (which is not a heck of a lot) ,
> that the average notification might be, say, 40 bytes of name plus
Peter Eisentraut wrote:
> Joshua D. Drake wrote:
>> Funny :). What can I do to help get 8.2.4 branched?
>
> There is no branching involved, but you can look into
> src/tools/RELEASE_CHANGES and see what things you want to help with.
> Getting a release changes list would be a start.
>
We're j
Joshua D. Drake wrote:
> Dave Page wrote:
>> Peter Eisentraut wrote:
>>> Joshua D. Drake wrote:
>>>> Funny :). What can I do to help get 8.2.4 branched?
>>> There is no branching involved, but you can look into
>>> src/tools/RELEASE_CHANGES and see w
Magnus Hagander wrote:
On Tue, Apr 03, 2007 at 06:16:26PM +0900, Hiroshi Saito wrote:
Slony-I is still used...Ahh, I have not confirmed it yet.
Slony uses it, yes. It would probably be worthwhile to fix that one as
well, but I haven't looked at how much work that would be.
And to port the bu
> --- Original Message ---
> From: Stefan Kaltenbrunner <[EMAIL PROTECTED]>
> To: Andrew Dunstan <[EMAIL PROTECTED]>
> Sent: 06/04/07, 15:33:20
> Subject: Re: [HACKERS] What X86/X64 OS's do we need coverage for?
>
> yeah improving windows coverage might be a nice thing - some other
I'm
> --- Original Message ---
> From: "Florian G. Pflug" <[EMAIL PROTECTED]>
> To: "pgsql-hackers@postgresql.org"
> Sent: 06/04/07, 20:12:39
> Subject: [HACKERS] Fate of pgsnmpd
>
> Hi
>
> Does anyone know if pgsnmpd is still actively developed?
> The last version (0.1b1) is about 15 mont
On Windows Vista, IPv6 is enabled by default, and cannot be uninstalled,
or disabled easily on the loopback adaptor. localhost is ::1 by
default, and the enhanced 'security' makes it insanely difficult to edit
the hosts file.
This means that the regression tests fail to run, leaving a
postmaster.
Andrew Dunstan wrote:
> Peter Eisentraut wrote:
>> Am Mittwoch, 11. April 2007 15:36 schrieb Dave Page:
>>
>>> This means that the regression tests fail to run, leaving a
>>> postmaster.log full of 'no pg_hba.conf entry for host ::1' errors.
>>&
Magnus Hagander wrote:
> On Wed, Apr 11, 2007 at 10:08:36AM -0400, Andrew Dunstan wrote:
>> Peter Eisentraut wrote:
>>> Am Mittwoch, 11. April 2007 15:36 schrieb Dave Page:
>>>
>>>> This means that the regression tests fail to run, leaving a
>>>&g
Magnus Hagander wrote:
On Thu, Apr 12, 2007 at 12:24:58AM +0200, Peter Eisentraut wrote:
Magnus Hagander wrote:
(FWIW, I had ipv6 on my list of things to make happen, but I didn't
realise it would cause this issue on a machine with ipv6 on it, since
I don't have one)
The IPv6 support is finely
301 - 400 of 1719 matches
Mail list logo
