On Fri, Mar 2, 2012 at 1:50 PM, Robert Haas wrote:
>> But is it unsurmountable? -- dlsym returns a function pointer, and one
>> would build up the operator table for the version of the extension at
>> hand, so one might have ltree "version 1.01" and ltree "version 2.3"
>> fields in the same databa
On Fri, Mar 2, 2012 at 1:53 PM, Daniel Farina wrote:
> On Fri, Mar 2, 2012 at 10:37 AM, Peter Eisentraut wrote:
>> On tis, 2012-02-28 at 11:00 -0800, Daniel Farina wrote:
>>> I'd really like to support libraries (C or otherwise) of multiple
>>> versions at the same time, when the underlying libra
On Fri, Mar 2, 2012 at 10:37 AM, Peter Eisentraut wrote:
> On tis, 2012-02-28 at 11:00 -0800, Daniel Farina wrote:
>> I'd really like to support libraries (C or otherwise) of multiple
>> versions at the same time, when the underlying library permits.
>
> What's preventing you from doing that now?
On tis, 2012-02-28 at 11:00 -0800, Daniel Farina wrote:
> I'd really like to support libraries (C or otherwise) of multiple
> versions at the same time, when the underlying library permits.
What's preventing you from doing that now? You need to name all the
symbols differently, of course.
--
S
On Sun, Feb 26, 2012 at 7:36 AM, Peter Eisentraut wrote:
> On lör, 2012-02-25 at 14:21 +0100, Christoph Berg wrote:
>> Well, I'm trying to invoke the extension's "make check" target at
>> extension build time. I do have a temporary installation I own
>> somehwere in my $HOME, but that is still try
On Sun, Feb 26, 2012 at 09:50:04PM -0500, Robert Haas wrote:
> On Sun, Feb 26, 2012 at 10:36 AM, Peter Eisentraut wrote:
> > On lör, 2012-02-25 at 14:21 +0100, Christoph Berg wrote:
> >> Well, I'm trying to invoke the extension's "make check" target at
> >> extension build time. I do have a tempor
On Fri, Feb 24, 2012 at 08:21:05PM +0200, Peter Eisentraut wrote:
> On fre, 2012-02-24 at 17:26 +0100, Sandro Santilli wrote:
> > We don't initdb with PostGIS regression testing framework
> > but I've considered doing it for this specific case and it stroke me
> > that even then we couldn't control
On Sun, Feb 26, 2012 at 10:36 AM, Peter Eisentraut wrote:
> On lör, 2012-02-25 at 14:21 +0100, Christoph Berg wrote:
>> Well, I'm trying to invoke the extension's "make check" target at
>> extension build time. I do have a temporary installation I own
>> somehwere in my $HOME, but that is still tr
On lör, 2012-02-25 at 14:21 +0100, Christoph Berg wrote:
> Well, I'm trying to invoke the extension's "make check" target at
> extension build time. I do have a temporary installation I own
> somehwere in my $HOME, but that is still trying to find extensions in
> /usr/share/postgresql/9.1/extension
Re: Peter Eisentraut 2012-02-24 <1330107599.32452.15.ca...@vanquo.pezone.net>
> On fre, 2012-02-24 at 11:53 -0500, Tom Lane wrote:
> > > We have the same problem with testing extensions at build-time in
> > the
> > > Debian packages. The server's SHAREDIR /usr/share/postgresql/... is
> > > only wri
On Fri, Feb 24, 2012 at 3:31 PM, Daniel Farina wrote:
> Having been in this position once before in a different but similar
> situation, there's one big caveat: initdb is *really* slow, so it is
> really painful for people who write Postgres-linked code that is
> compiled separately, whereby the i
On Fri, Feb 24, 2012 at 6:31 PM, Andrew Dunstan wrote:
> Really? Here's what I just got on a severely under-resourced SL6 VM:
>
> 1.5s doesn't seem terribly slow.
You are right. Come to think of it, I do seem to recall that initdb
got some speed improvements; these were in 8.3 days, I think.
Her
On 02/24/2012 06:31 PM, Daniel Farina wrote:
On Fri, Feb 24, 2012 at 10:21 AM, Peter Eisentraut wrote:
On fre, 2012-02-24 at 17:26 +0100, Sandro Santilli wrote:
We don't initdb with PostGIS regression testing framework
but I've considered doing it for this specific case and it stroke me
that
On Fri, Feb 24, 2012 at 10:21 AM, Peter Eisentraut wrote:
> On fre, 2012-02-24 at 17:26 +0100, Sandro Santilli wrote:
>> We don't initdb with PostGIS regression testing framework
>> but I've considered doing it for this specific case and it stroke me
>> that even then we couldn't control SHAREDIR.
On fre, 2012-02-24 at 17:26 +0100, Sandro Santilli wrote:
> We don't initdb with PostGIS regression testing framework
> but I've considered doing it for this specific case and it stroke me
> that even then we couldn't control SHAREDIR.
I would always create a new instance using initdb for test run
On fre, 2012-02-24 at 11:53 -0500, Tom Lane wrote:
> > We have the same problem with testing extensions at build-time in
> the
> > Debian packages. The server's SHAREDIR /usr/share/postgresql/... is
> > only writable by root, while the build is running as buildd user, so
> > there is no way to do "
Christoph Berg writes:
> Re: Sandro Santilli 2012-02-22 <20120222101656.GB6125@gnash>
>> I'm not really looking for "inline extensions".
>> I do want to install the extension objects somewhere, just NOT
>> in the PostgreSQL builtin SHAREDIR but in an arbitrary staging
>> directory to use for QA th
On Thu, Feb 23, 2012 at 06:53:05PM -0800, Daniel Farina wrote:
> On Tue, Feb 21, 2012 at 1:34 PM, Dimitri Fontaine
> wrote:
> > Sandro Santilli writes:
> > Please see the "inline extension" thread where answers to your problem
> > have been discussed.
>
> I'm pretty sure Sandro is hacking PostGI
On Fri, Feb 24, 2012 at 09:59:12AM +0100, Christoph Berg wrote:
> Re: Sandro Santilli 2012-02-22 <20120222101656.GB6125@gnash>
> > I'm not really looking for "inline extensions".
> > I do want to install the extension objects somewhere, just NOT
> > in the PostgreSQL builtin SHAREDIR but in an arbi
Daniel Farina writes:
> I'm pretty sure Sandro is hacking PostGIS, so inline extensions are of
> no help here.
Sorry about the sloppy mention, one of the things under discussion (but
out of scope for 9.2) in the inline extension thread is about where to
store the shared objects and extension file
Re: Sandro Santilli 2012-02-22 <20120222101656.GB6125@gnash>
> I'm not really looking for "inline extensions".
> I do want to install the extension objects somewhere, just NOT
> in the PostgreSQL builtin SHAREDIR but in an arbitrary staging
> directory to use for QA the extension before distributio
On Tue, Feb 21, 2012 at 1:34 PM, Dimitri Fontaine
wrote:
> Sandro Santilli writes:
> Please see the "inline extension" thread where answers to your problem
> have been discussed.
I'm pretty sure Sandro is hacking PostGIS, so inline extensions are of
no help here.
Can you tell us why alternative
On Tue, Feb 21, 2012 at 10:34:42PM +0100, Dimitri Fontaine wrote:
> Sandro Santilli writes:
> > On Tue, Feb 21, 2012 at 10:21:17AM -0500, Tom Lane wrote:
> >> Sandro Santilli writes:
> >> > I'm trying to understand what options I have to test "CREATE EXTENSION"
> >> > w/out installing the extensi
Sandro Santilli writes:
> On Tue, Feb 21, 2012 at 10:21:17AM -0500, Tom Lane wrote:
>> Sandro Santilli writes:
>> > I'm trying to understand what options I have to test "CREATE EXTENSION"
>> > w/out installing the extension files in their final destination.
>>
>> There aren't any. Generally spe
On Tue, Feb 21, 2012 at 10:21:17AM -0500, Tom Lane wrote:
> Sandro Santilli writes:
> > I'm trying to understand what options I have to test "CREATE EXTENSION"
> > w/out installing the extension files in their final destination.
>
> There aren't any. Generally speaking, if you want to be testing
Sandro Santilli writes:
> I'm trying to understand what options I have to test "CREATE EXTENSION"
> w/out installing the extension files in their final destination.
There aren't any. Generally speaking, if you want to be testing an
extension, you should be doing it in a test installation anyway;
I'm trying to understand what options I have to test "CREATE EXTENSION"
w/out installing the extension files in their final destination.
Could not find a way to set SHAREDIR from within psql, nor a way
to specify it in initdb call. Am I missing it something ?
PS: please include my address in repl
27 matches
Mail list logo
