robertmh...@gmail.com (Robert Haas) writes:
> On Fri, Jan 8, 2010 at 10:12 AM, Dave Page wrote:
>>> I have long spoken against making Windows a second class citizen. But I
>>> don't think David is going to do that (and I'll hound him if he does). But
>>> that doesn't mean it has to be fully suppor
Magnus Hagander wrote:
On Fri, Jan 8, 2010 at 18:48, Dave Page wrote:
2010/1/8 Magnus Hagander :
On Fri, Jan 8, 2010 at 18:44, Dave Page wrote:
The current set of active mirrors can always be found at
http://www.postgresql.org/mirrors.xml, so you can build URLs on the
mirror network using th
On Jan 8, 2010, at 10:08 AM, Magnus Hagander wrote:
> That, or implement that "send me to a random mirror" feature. Or
> maybe the "send me to a random close mirror if available, or a random
> global if not" feature. :-)
>
> Either way, there's definitely room for some improvement there, but
> l
On Fri, Jan 8, 2010 at 18:48, Dave Page wrote:
> 2010/1/8 Magnus Hagander :
>> On Fri, Jan 8, 2010 at 18:44, Dave Page wrote:
>>> The current set of active mirrors can always be found at
>>> http://www.postgresql.org/mirrors.xml, so you can build URLs on the
>>> mirror network using the protocol,
On Fri, Jan 8, 2010 at 18:55, David E. Wheeler wrote:
> On Jan 8, 2010, at 9:38 AM, Magnus Hagander wrote:
>
>> Is there a particular reason not to use the existing mirroring network
>> to distribute the files? If not, then I suggest using them should be
>> part of the design.
>
> No, as long as P
On Jan 8, 2010, at 9:59 AM, Dave Page wrote:
> Either can be arranged. For StackBuilder, we created a pgFoundry
> project, so files can just be uploaded there by authorised users, from
> where they get replicated back onto the mirror network.
>
> Which leads us neatly back to the GForge URL threa
On Fri, Jan 8, 2010 at 5:55 PM, David E. Wheeler wrote:
> On Jan 8, 2010, at 9:38 AM, Magnus Hagander wrote:
>
>> Is there a particular reason not to use the existing mirroring network
>> to distribute the files? If not, then I suggest using them should be
>> part of the design.
>
> No, as long as
On Jan 8, 2010, at 9:38 AM, Magnus Hagander wrote:
> Is there a particular reason not to use the existing mirroring network
> to distribute the files? If not, then I suggest using them should be
> part of the design.
No, as long as PAUS can drop uploaded distributions onto the master FTP server,
On Jan 8, 2010, at 9:24 AM, Dave Page wrote:
> If that is the goal of your project then I withdraw my previous
> comments, which were written on the belief that you were proposing a
> generic distribution/build/installation system for PostgreSQL users.
It is a generic distribution and installatio
2010/1/8 Magnus Hagander :
> On Fri, Jan 8, 2010 at 18:44, Dave Page wrote:
>> The current set of active mirrors can always be found at
>> http://www.postgresql.org/mirrors.xml, so you can build URLs on the
>> mirror network using the protocol, host, port and path from the mirror
>> list, and then
On Fri, Jan 8, 2010 at 18:44, Dave Page wrote:
> On Fri, Jan 8, 2010 at 5:38 PM, Magnus Hagander wrote:
>> On Thu, Jan 7, 2010 at 21:07, David E. Wheeler wrote:
>>> Hackers,
>>>
>>> I've posted a [plan] to implement PGAN][], a CPAN for PostgreSQL
>>> extensions. I've tried to closely follow the
On Fri, Jan 8, 2010 at 5:38 PM, Magnus Hagander wrote:
> On Thu, Jan 7, 2010 at 21:07, David E. Wheeler wrote:
>> Hackers,
>>
>> I've posted a [plan] to implement PGAN][], a CPAN for PostgreSQL extensions.
>> I've tried to closely follow the [CPAN philosophy][] to come up with a plan
>> that re
On Thu, Jan 7, 2010 at 21:07, David E. Wheeler wrote:
> Hackers,
>
> I've posted a [plan] to implement PGAN][], a CPAN for PostgreSQL extensions.
> I've tried to closely follow the [CPAN philosophy][] to come up with a plan
> that requires a minimum-work implementation that builds on the existin
On Fri, Jan 8, 2010 at 5:13 PM, David E. Wheeler wrote:
> Please let the Windows thread die now. PGAN doesn't ignore Windows; it
> ignores installer development.
>
yeah, I think there are two quite separable projects here. It's quite
possible that once the binary installer people have a source p
On Fri, Jan 8, 2010 at 5:13 PM, David E. Wheeler wrote:
> This whole bit about Windows is a red herring. Perhaps I should not have
> phrased it the way I did WRT Windows. So I'm going to change it to:
>
>> The PGAN client will make no other assumptions about how to build and
>> install extensio
On Jan 8, 2010, at 1:35 AM, Dave Page wrote:
> I am saying that if the design won't ever work without requiring
> painful dependency installation that users will likely not want to
> bother with, then it is fundamentally broken. Better to write one
> system that can _eventually_ work everywhere, t
Dave,
* Dave Page (dp...@pgadmin.org) wrote:
> Right - but the buildfarm isn't a feature being offered to end users.
And this network isn't a feature of the core code either, nor, do I
believe, is it being designed in a way that would require an overhaul
down the road to support Windows. To be h
On Fri, Jan 8, 2010 at 4:34 PM, Joshua D. Drake wrote:
> On Fri, 2010-01-08 at 16:33 +, Dave Page wrote:
>> On Fri, Jan 8, 2010 at 3:56 PM, Joshua D. Drake
>> wrote:
>> > On Fri, 2010-01-08 at 15:12 +, Dave Page wrote:
>> >> Hey Andrew
>> >>
>> >> On Fri, Jan 8, 2010 at 12:57 PM, Andrew
On Fri, 2010-01-08 at 16:33 +, Dave Page wrote:
> On Fri, Jan 8, 2010 at 3:56 PM, Joshua D. Drake
> wrote:
> > On Fri, 2010-01-08 at 15:12 +, Dave Page wrote:
> >> Hey Andrew
> >>
> >> On Fri, Jan 8, 2010 at 12:57 PM, Andrew Dunstan
> >> wrote:
> >> >
> >> > Windows came late to the bui
On Fri, Jan 8, 2010 at 3:56 PM, Joshua D. Drake wrote:
> On Fri, 2010-01-08 at 15:12 +, Dave Page wrote:
>> Hey Andrew
>>
>> On Fri, Jan 8, 2010 at 12:57 PM, Andrew Dunstan wrote:
>> >
>> > Windows came late to the buildfarm. According to the CVS log, the buildfarm
>> > client was first check
On Fri, 2010-01-08 at 15:12 +, Dave Page wrote:
> Hey Andrew
>
> On Fri, Jan 8, 2010 at 12:57 PM, Andrew Dunstan wrote:
> >
> > Windows came late to the buildfarm. According to the CVS log, the buildfarm
> > client was first checked in in Sept 2004, got initial Mingw support in Jan
> > 2005 a
On Fri, Jan 8, 2010 at 10:12 AM, Dave Page wrote:
>> I have long spoken against making Windows a second class citizen. But I
>> don't think David is going to do that (and I'll hound him if he does). But
>> that doesn't mean it has to be fully supported from day one.
>
> I'm not saying it should be
Hey Andrew
On Fri, Jan 8, 2010 at 12:57 PM, Andrew Dunstan wrote:
>
> Windows came late to the buildfarm. According to the CVS log, the buildfarm
> client was first checked in in Sept 2004, got initial Mingw support in Jan
> 2005 and MSVC support in March 2007, when we finally got some of the too
On Fri, Jan 8, 2010 at 15:14, Ron Mayer wrote:
> Magnus Hagander wrote:
>> On Fri, Jan 8, 2010 at 05:22, Ron Mayer
>> wrote:
>>> David E. Wheeler wrote:
On Jan 7, 2010, at 1:31 PM, Dave Page wrote:
> No, I'm suggesting the mechanism needs to support source and binary
> distribution.
Magnus Hagander wrote:
> On Fri, Jan 8, 2010 at 05:22, Ron Mayer wrote:
>> David E. Wheeler wrote:
>>> On Jan 7, 2010, at 1:31 PM, Dave Page wrote:
No, I'm suggesting the mechanism needs to support source and binary
distribution. For most *nix users, source will be fine. For Windows
Dave Page wrote:
The only reason we ever offer different functionality on different
platforms is when there are external reasons forcing us to - for
example, lack of reparse points in NTFS on Windows NT 4.0 prevented us
offering table space support, and for some time we had no Win32 port
of lib
On Fri, Jan 8, 2010 at 10:40 AM, Markus Wanner wrote:
> Hi,
>
> Josh Berkus wrote:
>>
>> Dave wrote:
>>>
>>> and frankly,
>>> isn't the way this project generally works.
>
> Isn't it? We didn't even support Windows for quite a long time.
No, it's quite different for the PostgreSQL not to support
Hi,
Josh Berkus wrote:
Dave wrote:
and frankly,
isn't the way this project generally works.
Isn't it? We didn't even support Windows for quite a long time. We still
have lots more active Unix developers and knowledge that Windows ones.
And isn't there some "scratch your own itch" philosophy
On Thu, Jan 7, 2010 at 10:07 PM, Josh Berkus wrote:
>> Building them is no problem - authors can easily use EC2 for which we
>> have an AMI pre-configured for next to no cost, can build on their own
>> platform, on a community provided system, or get a friend to do it.
>
> So any module author, in
On Fri, Jan 8, 2010 at 05:22, Ron Mayer wrote:
> David E. Wheeler wrote:
>> On Jan 7, 2010, at 1:31 PM, Dave Page wrote:
>>> No, I'm suggesting the mechanism needs to support source and binary
>>> distribution. For most *nix users, source will be fine. For Windows
>>> binaries are required.
>>
>>
On Jan 7, 2010, at 4:07 PM, Josh Berkus wrote:
> Building a simple solution which doesn't initially cover all bases but
> can be steadily improved is a far superior strategy to trying to spec
> The Perfect Solution before even starting work. And if we want to keep
> recruiting new contributors, cr
David E. Wheeler wrote:
> On Jan 7, 2010, at 1:31 PM, Dave Page wrote:
>> No, I'm suggesting the mechanism needs to support source and binary
>> distribution. For most *nix users, source will be fine. For Windows
>> binaries are required.
>
> I would love to follow what Strawberry Perl has done to
* Dave Page (dp...@pgadmin.org) wrote:
> Because if we (PostgreSQL) are going to support this effort, then it
> should not ignore such a huge percentage of our installation base.
Not doing it day 1 is not ignoring. It's using what resources *are*
being made available to the best extent we can. I
* Josh Berkus (j...@agliodbs.com) wrote:
> What I'm getting from your e-mail, Dave, is "If it doesn't solve all
> problems for everyone in the world from Day 1, it's not worth doing."
> It's my experience that the way to get OSS software that works is to
> build a little bit at a time, each deliver
On Thu, Jan 07, 2010 at 12:07:19PM -0800, David Wheeler wrote:
> Hackers,
>
> I've posted a [plan] to implement PGAN][], a CPAN for PostgreSQL
> extensions. I've tried to closely follow the [CPAN philosophy][] to
> come up with a plan that requires a minimum-work implementation that
> builds on th
Dimitri Fontaine writes:
> e.g. pg_execute_commands_from_file('path/ to/file.sql'). It would not
[...]
> Then you need to add a catalog for holding the extensions metadata, like
[...]
> Now you can hack a CREATE EXTENSION command to fill-in the catalog, and
> the commands INSTALL EXTENSION and DRO
On Jan 7, 2010, at 2:23 PM, Dimitri Fontaine wrote:
> Maybe with a link to:
> http://www.postgresql.org/docs/8.4/static/extend.html
Good call, thanks.
David
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/
"David E. Wheeler" writes:
> On Jan 7, 2010, at 2:11 PM, Peter Eisentraut wrote:
>
>> You might want to clarify in your prose what an "extension" is. I
>> suspect I know what you mean, but perhaps not everyone does.
>
> Good suggestion, thanks. How about this in the FAQ?
>
> * WTF is an "extensi
On Jan 7, 2010, at 2:11 PM, Peter Eisentraut wrote:
> You might want to clarify in your prose what an "extension" is. I
> suspect I know what you mean, but perhaps not everyone does.
Good suggestion, thanks. How about this in the FAQ?
* WTF is an "extension"?
An extension is a piece of softwar
On tor, 2010-01-07 at 12:07 -0800, David E. Wheeler wrote:
> I've posted a [plan] to implement PGAN][], a CPAN for PostgreSQL extensions.
> I've tried to closely follow the [CPAN philosophy][] to come up with a plan
> that requires a minimum-work implementation that builds on the existing
> Post
On Jan 7, 2010, at 1:59 PM, Joshua D. Drake wrote:
> So +1 on Wheeler's idea.
Thanks!
David
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
> Building them is no problem - authors can easily use EC2 for which we
> have an AMI pre-configured for next to no cost, can build on their own
> platform, on a community provided system, or get a friend to do it.
So any module author, in order to submit any module, would be required
to build bin
On Thu, 2010-01-07 at 13:22 -0800, Josh Berkus wrote:
> Dave,
> What I'm getting from your e-mail, Dave, is "If it doesn't solve all
> problems for everyone in the world from Day 1, it's not worth doing."
I doubt that is Dave's intent because then we might as well stop work on
PostgreSQL too.
>
Dave Page writes:
> We have discussed this sort of facility at previous developer
> meetings, and as I recall came to the conclusion that we need to have
> the ability to distribute pre-built binaries, not just source code as
> virtually no Windows users are ever going to have a build environment
On Jan 7, 2010, at 1:31 PM, Dave Page wrote:
> No, I'm suggesting the mechanism needs to support source and binary
> distribution. For most *nix users, source will be fine. For Windows
> binaries are required.
I would love to follow what Strawberry Perl has done to solve this problem. In
2.0.
B
On Thu, Jan 7, 2010 at 9:22 PM, Josh Berkus wrote:
> Dave,
>
>> Whilst the aim is a noble one, glossing over 'it won't work on
>> Windows' which is by far our most popular platform these days seems
>> incredibly short sighted, and liable to lead to an endless stream of
>> 'why doesn't this work' q
On Jan 7, 2010, at 12:36 PM, Dave Page wrote:
> Whilst the aim is a noble one, glossing over 'it won't work on
> Windows' which is by far our most popular platform these days seems
> incredibly short sighted, and liable to lead to an endless stream of
> 'why doesn't this work' questions. It also d
Dave,
> Whilst the aim is a noble one, glossing over 'it won't work on
> Windows' which is by far our most popular platform these days seems
> incredibly short sighted, and liable to lead to an endless stream of
> 'why doesn't this work' questions. It also does the module authors no
> favours, by
David E. Wheeler wrote:
> Hackers,
>
> I've posted a [plan] to implement PGAN][], a CPAN for PostgreSQL
> extensions. I've tried to closely follow the [CPAN philosophy][] to
> come up with a plan that requires a minimum-work implementation that
> builds on the existing PostgreSQL tools and the exa
On Thu, Jan 7, 2010 at 21:42, Joshua D. Drake wrote:
> On Thu, 2010-01-07 at 20:36 +, Dave Page wrote:
>> On Thu, Jan 7, 2010 at 8:07 PM, David E. Wheeler
>> wrote:
>> > Hackers,
>> >
>> > I've posted a [plan] to implement PGAN][], a CPAN for PostgreSQL
>> > extensions. I've tried to closel
On Thu, 2010-01-07 at 20:36 +, Dave Page wrote:
> On Thu, Jan 7, 2010 at 8:07 PM, David E. Wheeler wrote:
> > Hackers,
> >
> > I've posted a [plan] to implement PGAN][], a CPAN for PostgreSQL
> > extensions. I've tried to closely follow the [CPAN philosophy][] to come up
> > with a plan that
On Thu, Jan 7, 2010 at 8:07 PM, David E. Wheeler wrote:
> Hackers,
>
> I've posted a [plan] to implement PGAN][], a CPAN for PostgreSQL extensions.
> I've tried to closely follow the [CPAN philosophy][] to come up with a plan
> that requires a minimum-work implementation that builds on the exist
Hackers,
I've posted a [plan] to implement PGAN][], a CPAN for PostgreSQL extensions.
I've tried to closely follow the [CPAN philosophy][] to come up with a plan
that requires a minimum-work implementation that builds on the existing
PostgreSQL tools and the examples of the [CPAN][] and [JSAN][
53 matches
Mail list logo
