- but then so do a
bunch of other OSI approved licences.
As Tom says though, the effect this has on users is zero. The licence
is still the same as its always been, regardless of what we say it is
based on or looks like.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
PGDay.EU 2009 C
.
> ISTM we should apply to OSI for approval of our licence, so we can then
> refer to it as the PostgreSQL licence. That then avoids any situation
> that might allow someone to claim some injunctive relief of part of the
> licence because of it being widely misdescribed.
Already in
On Mon, Oct 26, 2009 at 1:47 PM, Simon Riggs wrote:
> On Mon, 2009-10-26 at 13:13 +0000, Dave Page wrote:
>
>> > ISTM we should apply to OSI for approval of our licence, so we can then
>> > refer to it as the PostgreSQL licence. That then avoids any situation
>>
s about if PostgreSQL is being
> sold just as MySQL was...
Changing the licence is *not* going to happen.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
PGDay.EU 2009 Conference: http://2009.pgday.eu/start
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make change
On Mon, Oct 26, 2009 at 4:15 PM, Jaime Casanova
wrote:
> On Mon, Oct 26, 2009 at 10:40 AM, Dave Page wrote:
>> On Mon, Oct 26, 2009 at 3:36 PM, Jaime Casanova
>> wrote:
>>> On Mon, Oct 26, 2009 at 8:08 AM, Simon Riggs wrote:
>>>>
>>>> ISTM we sho
On Mon, Oct 26, 2009 at 4:25 PM, Tom Lane wrote:
> Dave Page writes:
>> On Mon, Oct 26, 2009 at 4:15 PM, Jaime Casanova
>> wrote:
>>> to tell someone we no longer label our license as "simplified BSD" but
>>> as MIT is, in the eyes and mind of use
On Mon, Oct 26, 2009 at 7:02 PM, Chris Browne wrote:
> dp...@pgadmin.org (Dave Page) writes:
>> As Tom says though, the effect this has on users is zero. The licence
>> is still the same as its always been, regardless of what we say it is
>> based on or looks like.
>
On Friday 30 November at 1200 GMT, the server that hosts our primary
FTP server, GIT server and one of the website mirrors will be moved to
a new data center. Downtime is expected to be two to three hours.
Apologies for any inconvenience this may cause.
--
Dave Page
EnterpriseDB UK: http
On Thu, Oct 29, 2009 at 9:35 AM, Dave Page wrote:
> On Friday 30 November at 1200 GMT, the server that hosts our primary
> FTP server, GIT server and one of the website mirrors will be moved to
> a new data center. Downtime is expected to be two to three hours.
>
> Apologies for an
t affects all of the
packagers to varying degrees and should not be overlooked.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
PGDay.EU 2009 Conference: http://2009.pgday.eu/start
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscript
as I'm sure you're already thinking it, yes, I know it doesn't
help if the new table is created using psql, but there are lots of
shops where pgAdmin is the default tool, and it could help them and
just exhibit the current behaviour if someone does break out psql.
--
Dave Page
Ente
they required to contribute even more of their time to
review as well, just to help their own occasional code contributions
get through the process?
(yes, I am thinking largely of me, working tens of hours per week on
Postgres, but perhaps submiting one relatively small patch per
release)
--
everyone
chipping in, and I do try to do so myself on appropriate patches (for
example, the recent Windows DACL bug fix which I spent a few hours
reviewing and testing - and am still waiting for Magnus to commit
:-p). I just think that *requiring* people to review will ultimately
be counter producti
> What about pg_dump/psql setting fallback_application_name?
Per Tom, I'm waiting on the possible new array-based libpq connect API
which will make a conversion of those utilities from PQsetdbLogin a
lot cleaner than moving to PQconnectdb (and all the ugly connection
string building that wo
f which they have little or no
understanding (which may well be an issue at times).
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
s pretty
> ubiquitous - in fact, given that we now support Windows, arguably more
> so than awk.
Building in VC++ on Windows already requires Perl. And if you're
building in mingw, you've probably already got it, or can get it
pretty easily.
--
Dave Page
EnterpriseDB UK: http://ww
On Fri, Nov 13, 2009 at 4:12 PM, Robert Haas wrote:
> Yep, it's only on UNIX-ish systems where Perl isn't necessarily
> required, and realistically I think it is probably present on nearly
> all of those, too.
Exactly.
--
Dave Page
EnterpriseDB UK: http://www.enterprised
On Wed, Nov 25, 2009 at 1:22 PM, Andres Freund wrote:
> Hi,
>
> On Thursday 22 October 2009 15:07:13 Dave Page wrote:
>> Updated patch attached. Per discussion, this:
>>
>> - Changes the envvar name to PGAPPNAME
>> - Removes support for setting application_n
en(newval) + 1);
repval[0] = 0;
for (x=0; x 126)
repval[x] = '?';
else
repval[x] = newval[x];
}
repval[x+1] = 0;
return repval;
}
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Updated application name patch, including a GUC assign hook to clean
the application name of any unsafe characters, per discussion.
Regards, Dave
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
appname-v4.diff
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql
On Sat, Nov 28, 2009 at 11:47 PM, Tom Lane wrote:
> Dave Page writes:
>> Updated application name patch, including a GUC assign hook to clean
>> the application name of any unsafe characters, per discussion.
>
> Applied with assorted editorialization. There were a cou
seems like an excessively ugly solution :) But what about the others?
> What would people prefer?
I like option 1 the best. Minimally invasive, and probably easier to
handle on the client than 2. 3 is just ugly as you say. You should be
ashamed of yourself :-p
--
Dave Page
EnterpriseDB
-
namely that too many brain dead hosting providers won't add a contrib
module or anything else in a customer's database because they don't
understand that just because it's not there by default doesn't mean
it's in any way second rate. Including pl/pgsql in template1 wil
usly just for testing. Should we just turn it on by
> default and see if anyone complains?
I say go for it. We'll soon know if it kills the buildfarm.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Oracle-compatible database company
---
of libpq.dll. The daily build number was the
most maintenance-free way of getting a fourth value for the version
resource.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Oracle-compatible database company
---(end of broadcast)---
TIP 6: explain analyze is your friend
On Mon, Feb 25, 2008 at 10:03 PM, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Dave Page wrote:
> > It's used on Windows to ensure that installers can do the right thing
> > when replacing a copy of libpq.dll. The daily build number was the
> > most maintena
On Mon, Feb 25, 2008 at 11:48 PM, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Dave Page wrote:
> > Yes, because newer builds may be linked against updated runtime
> > versions. We need to be sure the installer will upgrade the file so it
> > definitely mat
help to many people's
>
> Comments from others? Objections?
If it's well documented which versions of MSVC++ work with it, and
which versions of ossp-uuid, I don't see it as a major problem to
include it. It's annoying for sure, but it's not the end of the worl
es ;)
We are - but the idea doesn't need to be on the list for us to
consider it. Just write up a good project outline and plan ready to
submit when the doors open.
--
Dave Page
EnterpriseDB UK Ltd: http://www.enterprisedb.com
PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk
-
ak at a
specific point, I sometimes add a loop to the code along the lines of:
int x=0;
while (!x)
Sleep(100);
When the backend hits that point, attach the debugger, break
execution, and set x to a value in the locals window. Then you can
step through the code from that point.
--
Dave
x27;t account for problems discovered post-release.
>
> It is a best effort with our limited resources.
Should we outsource it? It is user-facing :-p
--
Dave Page
EnterpriseDB UK Ltd: http://www.enterprisedb.com
PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk
--
Sent via pgsql-ha
per wiki
into a dedicated area on it.
Any thoughts on whether thats a good or bad idea? Any objections?
--
Dave Page
EnterpriseDB UK Ltd: http://www.enterprisedb.com
PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
't see any reason why what Greg & Josh are suggesting couldn't
work - it's roughly what I had in mind anyway, except that we'd have
to use a URL rewrite on developer to get it to redirect requests to
wiki, as that hostname is used for other things so hijacking DNS
doesn'
onical name = distrib-coffee.ipsl.jussieu.fr.
Name: distrib-coffee.ipsl.jussieu.fr
Address: 134.157.176.20
--
Dave Page
EnterpriseDB UK Ltd: http://www.enterprisedb.com
PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.or
o explain the details to someone who does.
I was actually thinking of the OS X buildfarm member I setup to
exercise this. From your description it sounded like we need to
generate the probe header manually if we enable dtrace.
I'm sure Magnus would love to hear the details for the MSVC perl sc
in the buildfarm to create the header file?
--
Dave Page
EnterpriseDB UK Ltd: http://www.enterprisedb.com
PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk
--
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, Mar 18, 2008 at 11:48 AM, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Am Dienstag, 18. März 2008 schrieb Dave Page:
>
> > I was actually thinking of the OS X buildfarm member I setup to
> > exercise this. From your description it sounded like we need to
>
emails should not rely on
> external domains. That way the project is in control, not the other way
> around.
The company domain is from the message id by the looks of it - it
should not be changed under any circumstances.
--
Dave Page
EnterpriseDB UK Ltd: http://www.enterprisedb.com
Pos
gets 5
threads that's not a huge chore).
I see no reason to go manually copying all 2k emails to the wiki.
--
Dave Page
EnterpriseDB UK Ltd: http://www.enterprisedb.com
PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk
--
Sent via pgsql-hackers mailing list (pgsql-hackers@post
g00131.php
Patch queue -> Wiki]
To link to another wiki page, put the target page title in double
square brackets
[[Developer and Contributor Resources]]
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
not enough space.
As I read it, each node takes the value of the largest child, not the
sum of the children.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
he required space for the file it's
copying, thus checking the file size to verify that the copy has
completed is not a valid test.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
tried it, and
> then wouldn't be surprised if it behaved either way :-)
It pre-allocates the space as copy does. And yes, I did test :-p
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To m
having it always on.
Sounds reasonable to me.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
erned about the back
> branches where testing isn't as complete.
We'll find out in a few hours.
My guess is that anyone happy to be running such an old version of
gettext is probably running old versions of everything, including PG.
Your case is obviously a little different.
--
a structures), not query results.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ink the idea is that WAL records would be shipped (possibly via
> socket) and applied as they're generated, rather than on a
> file-by-file basis. At least that's what "real-time" implies to me...
Yes, we're talking real-time streaming (synchronous) log shipping.
--
Da
On Thu, May 29, 2008 at 4:52 PM, Dave Page <[EMAIL PROTECTED]> wrote:
> On Thu, May 29, 2008 at 4:45 PM, Justin <[EMAIL PROTECTED]> wrote:
>>
>> Then what is the purpose of shared buffers if nothing is being reused is it
>> only used to keep track locks, change
es are valid, as
>> someone
>> else mentioned elsewhere in this thread.
>
> pg_ctl -D data check?
>
> I would +1 that.
I would also really like to see that - though I'd also like to see an
SQL interface so we can check a config before saving when editing via
pgAdmin or simi
tput PKST as a timezone (in a
'timestamp with time zone'), but won't accept it back in. Perhaps we
should only output names that we can read back, and revert to a
numeric offset in other cases?
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hacke
On Tue, Jun 10, 2008 at 4:37 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Dave Page" <[EMAIL PROTECTED]> writes:
>> It seems like a bug that we happily output PKST as a timezone (in a
>> 'timestamp with time zone'), but won't accept it ba
On Tue, Jun 10, 2008 at 4:51 PM, Alvaro Herrera
<[EMAIL PROTECTED]> wrote:
> Dave Page wrote:
>> Right, but shouldn't we always output something we know we can read
>> back in (unambiguously), assuming a server with no user defined
>> abbreviations?
>
> Tha
On Wed, Jun 11, 2008 at 6:56 PM, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> Dave Page wrote:
>> On Mon, Jun 2, 2008 at 5:46 AM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
>>
>> > pg_ctl -D data check?
>> >
>> > I would +1 that.
>>
>&
ent packages from Cygwin themselves are 8.2.5.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
mments, should I register on wiki? And potentially make some
> actual reviewers to skip the patch?
In that situation, just add your comments to the wiki page using the
appropriate template, but don't bother to list yourself as a reviewer
(for the very reason you suggest).
On Wed, Jul 2, 2008 at 11:44 AM, Marko Kreen <[EMAIL PROTECTED]> wrote:
> On 7/2/08, Dave Page <[EMAIL PROTECTED]> wrote:
>> On Wed, Jul 2, 2008 at 11:37 AM, Marko Kreen <[EMAIL PROTECTED]> wrote:
>> > I don't understand one aspect - if I'm unfamiliar
patches for people to look over, and don't be afraid to ask if you're
not sure about something.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
atforms to support).
I would suggest generating just VC2k5 project files, and then
modifying the build scripts to upgrade them first if required. We do
something similar with wxWidgets for pgAdmin's use - albeit converting
VC++6 files to 2k5 - using the /upgrade option in vcbuild.exe. I
assume som
- new patches to the September page!
Regards, Dave
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Thu, Jul 3, 2008 at 8:02 PM, Marko Kreen <[EMAIL PROTECTED]> wrote:
> On 7/3/08, Dave Page <[EMAIL PROTECTED]> wrote:
>> it concerns me that despite it being day 3 of the July commit fest,
>> people are still being advised to add new items to the wiki page.
>&
to a list sometime in
the past couple of months) before it starts, otherwise organisation of
reviewers and completion of the Fest becomes chaotic for all and a
nightmare task for the CommitFest manager.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing lis
ity for ensuring the
patch is listed on time. What we don't want is forgotten patches
getting added at the last minute, right as the CommitFest manager is
wrapping things up having got 95% of the patches reviewed and the
other 5% in progress.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.c
tly trying to close out". But you are not
> helping matters by trying to eliminate the distinction.
Agreed - but Robert does have a point - I know both Greg & I have
resorted to searching to find the in-progress fest page. I'll see if I
can improve the index page a little.
--
Da
On Mon, Jul 7, 2008 at 6:36 PM, Josh Berkus <[EMAIL PROTECTED]> wrote:
> Dave Page wrote:
>>
>> it concerns me that despite it being day 3 of the July commit fest,
>> people are still being advised to add new items to the wiki page.
>>
>> To make the idea
e to submit new
> patches" and "the place we are trying to commit patches from".
Well we have two separate links now, with hints as to their usage:
# Upcoming CommitFest - add new patches here
# In-progress CommitFest - patch review underway here
--
Dave Page
EnterpriseDB UK:
ders, we're a FOSS project working for our end users. If
we can include an important and popular feature like this at the
expense of a few weeks extra wait for the release, it seems to me that
we'll be serving our users far better overall than making a fair
percentage of them wait ano
gested a couple of weeks for the outstanding issues he's
aware of.
If there are fundamental problems which will take 10 - 12 months to
resolve to our normal standards, then I do believe 8.5 would be more
appropriate.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent vi
On Mon, Jan 26, 2009 at 4:20 PM, Tom Lane wrote:
> Dave Page writes:
>> On Mon, Jan 26, 2009 at 3:58 PM, Tom Lane wrote:
>>> This is pretty much exactly how I see it. *Hot standby is not ready*,
>
>> So can you give us an idea of what parts of the code are in n
I don't buy that. Sure, sync-rep would be the icing on the cake, but
HS with a small archive_timeout (even of the order of 10 or 15
minutes) would have been extremely useful on a number of systems I
used to run.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent
e this yet
(Windows 7 documentation is somewhat thin on the ground at the
moment), but the patch avoids theporblem by only setting
JOB_OBJECT_UILIMIT_HANDLES on earlier OSs.
Tested on CVS head, but should probably be backpatched to 8.3 to avoid
more bug reports.
--
Dave Page
EnterpriseDB
On Tue, Jan 27, 2009 at 11:04 AM, Heikki Linnakangas
wrote:
> Dave Page wrote:
>>
>> The attached patch adds support for the Windows 7 beta which we've had
>> a few reports of incompatibility with. When we startup using pg_ctl on
>> Windows, we create a job object
On Tue, Jan 27, 2009 at 11:26 AM, Peter Eisentraut wrote:
> On Tuesday 27 January 2009 12:34:56 Dave Page wrote:
>> I'm not entirely sure what has change in the SCM to cause this yet
>> (Windows 7 documentation is somewhat thin on the ground at the
>> moment), but the
On Tue, Jan 27, 2009 at 11:38 AM, Magnus Hagander wrote:
> Peter Eisentraut wrote:
>> On Tuesday 27 January 2009 12:34:56 Dave Page wrote:
>>> I'm not entirely sure what has change in the SCM to cause this yet
>>> (Windows 7 documentation is somewhat thin on the gr
o meet the requirements of the community without
getting bogged down in bike shedding.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
rk and estimates based on email
traffic.
If we do not, we will rapidly find that no company wants to sponsor
features for PostgreSQL in the future for fear that their money will
be wasted even if they jump through all the right hoops.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
iven that we made a point of porting
everything to C to avoid using any scripting languages on end-user
machines when we ported to Windows, it seems strange to relax that
'policy' now for convenience.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hacker
On Tue, Jan 27, 2009 at 2:49 PM, Alvaro Herrera
wrote:
> Dave Page wrote:
>> On Tue, Jan 27, 2009 at 2:39 PM, Alvaro Herrera
>> wrote:
>>
>> > I think it's fairly easy to install Perl on Windows actually. It
>> > doesn't sound too o
;t find out (and even then, I wouldn't hold
my breath for something like this).
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
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, Jan 27, 2009 at 3:40 PM, Tom Lane wrote:
> Dave Page writes:
>
>> We must at least have the solid belief (of a committer that that has
>> done a proper review) that a patch cannot be polished in an
>> appropriate timeframe,
>
> I already pointed out some pr
On Tue, Jan 27, 2009 at 3:48 PM, Joshua D. Drake wrote:
> On Tue, 2009-01-27 at 14:10 +0000, Dave Page wrote:
>> On Tue, Jan 27, 2009 at 2:01 PM, Peter Eisentraut wrote:
>>
>> > Updatable views is reverted. I agree that we should reject the rest and
>> > prepar
The
> idea of shipping it with only a minimal amount of testing should scare
> the pants off you.
It scares me for sure, but I'm reassured because I know and trust the
guys at 2ndQuadrant who have been testing extensively, as well as
other people such as Merlin and Heikki. Most pa
On Tue, Jan 27, 2009 at 4:42 PM, Peter Eisentraut wrote:
> On Tuesday 27 January 2009 17:47:52 Dave Page wrote:
>> The primary case that I'm objecting to is HS which you've
>> been saying will take 10 - 12 months to complete having by your own
>> admission not loo
On Tue, Jan 27, 2009 at 5:20 PM, Tom Lane wrote:
> Dave Page writes:
>> Not basing our release schedule on our commitments to shareholders is
>> an entirely different thing to treating sponsors of major features
>> like crap by arbitrarily bouncing the patches they'v
On Tue, Jan 27, 2009 at 7:04 PM, Zdenek Kotala wrote:
>
> Dave Page píše v út 27. 01. 2009 v 14:56 +:
>> I'd rather it was written in an appropriate language before feature
>> freeze, not in a language that makes it easier for the author but a
>> shade harder
On Tue, Jan 27, 2009 at 8:31 PM, Zdenek Kotala wrote:
>
> Dave Page píše v út 27. 01. 2009 v 19:36 +:
>> On Tue, Jan 27, 2009 at 7:04 PM, Zdenek Kotala wrote:
>> >
>> > Dave Page píše v út 27. 01. 2009 v 14:56 +:
>> >> I'd rather it was wr
s
something you wanted to include though.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
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, Jan 27, 2009 at 8:54 PM, Peter Eisentraut wrote:
> On Tuesday 27 January 2009 21:36:01 Dave Page wrote:
>> If it's been around for a year, why hasn't it been
>> submitted long ago so we could have rewritten and reviewed etc. in
>> plenty of time?
>
>
r our Windows users when
people start talking about changing the libpq API (for those that
don't know, Windows doesn't have DLL versioning like Unix - so any
non-backwards compatible API change really needs a corresponding
filename change to avoid pain and suffering).
--
Dave
On Tue, Feb 10, 2009 at 5:05 PM, Merlin Moncure wrote:
> PQinitSSL(SSL_ONLY) or something, where the constant is carefully
> chosen to not be accidentally passed in by older libpq users.
Ahh, OK. That would be painless.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
o save the system details
to a text file.
You should check the file to make sure there's nothing in there you
don't want to be public, and the zip it up and mail it to the list (CC
me incase the file is still too big for the list). I think you'll also
need to rename it to report.zi_
versions
worked with PG, but I haven't tried in quite a while. Might be worth
trying removing that too.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
nd/foreign/Makefile?rev=1.2
broke Mkvcbuild.pm. The attached patch just comments out the offending
code in Mkvcbuild.pm - I assume Peter will be putting the FDW stuff
back in 8.5.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
fdw.patch
Description: Binary data
--
Sent via pgsql-h
bump it yet
(unless Heikki wants to look at the other patches).
I agree that this patch alone should not delay the release further though.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to you
the import libraries for Kerberos, so where are the
DLLs?
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
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, Feb 27, 2009 at 9:39 AM, Magnus Hagander wrote:
> Dave Page wrote:
>> On Fri, Feb 27, 2009 at 8:47 AM, Zeugswetter Andreas OSB sIT
>> wrote:
>>> We should delayload this dll since it is only needed
>>> for specific configuration. No need to install when
would be far better spent on new features
than uglifying the code in far nastier ways than the current state of
the catalogs?
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://
adding
support for a new version with a different catalog schema.
Besides - what percentage of users ever go anywhere near the
catalogs? I'd guess a fraction of a percent of users, and maybe 1 - 5%
of developers.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-
orth his salt uses system catalogs. Lowering the barrier on
> uses these catalogs will lead to better and more useful tools as well.
Then psql and pgAdmin aren't doing their jobs properly. Tell us what you need.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-hac
On Wed, Mar 4, 2009 at 9:24 PM, Bill Moran wrote:
> In response to Dave Page :
>
> Don't those folks have to tweak their code with each new release anyway?
> Because those tables are constantly changing? I know we hit problems
> with the way triggers are stored in 8.3
On Sun, Mar 8, 2009 at 5:03 AM, Robert Haas wrote:
>
> The original patch was submitted by Koichi Suzuki - quite a few other
> people have looked at it and provided comments. Simon Riggs was
> assigned as the original reviewer, but for some reason Dave Page
> removed his name from
801 - 900 of 1719 matches
Mail list logo
