On Sun, 31 Jan 2010 22:24:40 +
Mark Cave-Ayland wrote:
> Ivan Sergio Borgonovo wrote:
>
> > Of course I can write a script that can workaround this.
> > It seems that the only thing missing is that pgxs 8.3 used to
> > prefix .so with lib and then rename them at install time, but
> > pgxs 8.
Ivan Sergio Borgonovo wrote:
Of course I can write a script that can workaround this.
It seems that the only thing missing is that pgxs 8.3 used to
prefix .so with lib and then rename them at install time, but pgxs
8.4 build them directly without prefix.
I'm just speculating this is the issue an
Ivan Sergio Borgonovo writes:
> Being able to compile and install an extension without a full dev
> environment
is nonsense.
> and without being root
That's easy on a development environment, but you keep insisting in not
having one. Now that's your problem.
> Sorry if it seemed I was complai
Hi,
Ivan Sergio Borgonovo writes:
> But considering that what it's really missing between what I need
> and what I get is renaming a file... it's just a pain I've to set up
> a whole new instance of postgres, install the whole source etc...
Untrue. Get the sources with git clone, them
./config
Ivan Sergio Borgonovo wrote:
When I'd like to try something new I'd like to put myself in the
most diffused, standard environment eg. one thing I'd like to avoid
is choosing my own flavour of compile options.
This is just nonsense, as we have explained to you several times and you
keep
On Sun, 31 Jan 2010 02:44:13 -0200
Euler Taveira de Oliveira wrote:
> Ivan Sergio Borgonovo escreveu:
> > I'm pretty sure that what you're pointing at is not going to work
> > unless you specify a bunch of other parameters.
> Ugh? Are you saying there is something wrong in our *official*
> docum
Ivan Sergio Borgonovo escreveu:
> I'm pretty sure that what you're pointing at is not going to work
> unless you specify a bunch of other parameters.
>
Ugh? Are you saying there is something wrong in our *official* documentation?
It is just a normal compilation command; if you're a C programmer yo
Aidan Van Dyk wrote:
* Andrew Dunstan [100130 19:55]:
If I am developing, say, a new
perl facility, I expect to develop and test using a private installation
of perl, and not screw up my system's perl. It's the same with postgres.
But, p
* Andrew Dunstan [100130 19:55]:
> If I am developing, say, a new
> perl facility, I expect to develop and test using a private installation
> of perl, and not screw up my system's perl. It's the same with postgres.
But, perl was a bad example. If y
On Sat, Jan 30, 2010 at 04:50:11PM -0700, James William Pye wrote:
> That install of PG that you're using will *probably not* have debugging
> information.
>
> Now, granted, you might not need PG with debugging for some problems, but
> chances are that you'll come across one (or two or fifty or s
On Sat, 30 Jan 2010 22:25:32 -0200
Euler Taveira de Oliveira wrote:
> Ivan Sergio Borgonovo escreveu:
> > That's pretty expensive.
> >
> Ugh?
>
> > I mean... I just would like my .so end up with the expected name
> > somewhere else.
> It's just two command lines [1].
Consider I'm absolutely ne
Ivan Sergio Borgonovo wrote:
Now my main concern is making my C code work in a reasonably decent
development environment. I hope if I'll ever succeed to take this
project to an end before being forced to take care of other stuff,
my code or my documented experience will come useful to others.
On Sat, 30 Jan 2010 18:32:58 -0500
Robert Haas wrote:
> On Sat, Jan 30, 2010 at 5:36 PM, Ivan Sergio Borgonovo
> wrote:
> >> For development purposes you would be far better off building a
> >> private version of postgres (with configure --prefix=/path) and
> >> using its pgxs to build, install
Ivan Sergio Borgonovo escreveu:
> That's pretty expensive.
>
Ugh?
> I mean... I just would like my .so end up with the expected name
> somewhere else.
It's just two command lines [1].
> Wouldn't it be better if make install could install stuff where I
> ask so I could put modules in different pl
On Jan 30, 2010, at 3:36 PM, Ivan Sergio Borgonovo wrote:
>> For development purposes you would be far better off building a
>> private version of postgres (with configure --prefix=/path) and
>> using its pgxs to build, install and test your module.
>
> That's pretty expensive.
eh:
j...@torch[]:
On Sat, Jan 30, 2010 at 5:36 PM, Ivan Sergio Borgonovo
wrote:
>> For development purposes you would be far better off building a
>> private version of postgres (with configure --prefix=/path) and
>> using its pgxs to build, install and test your module.
>
> That's pretty expensive.
How? I rebuil
Ivan Sergio Borgonovo wrote:
I'm absolutely aware I can't ask features unless someone is willing
to implement them or is paid for... but the easier/cheaper it is to
build up a dev/test environment the more people will try to
build/test something for postgres.
I do all my build/test work on U
On Sat, 30 Jan 2010 16:51:44 -0500
Andrew Dunstan wrote:
> Ivan Sergio Borgonovo wrote:
> > It is becoming a more serious issue than what I thought...
> > Debian install everything in
> > /usr/lib/postgresql/8.3/lib/
> > -rw-r--r-- 1 root root
> > so definitively it would be hard to write there
Ivan Sergio Borgonovo wrote:
On Sat, 30 Jan 2010 11:06:02 -0500
Tom Lane wrote:
Ivan Sergio Borgonovo writes:
... I can't make install (provided it works as expected, I
didn't try yet) since I sincerely hope that my user doesn't have
write right on whatever is pointed by $libdir.
On Sat, 30 Jan 2010 11:06:02 -0500
Tom Lane wrote:
> Ivan Sergio Borgonovo writes:
> > ... I can't make install (provided it works as expected, I
> > didn't try yet) since I sincerely hope that my user doesn't have
> > write right on whatever is pointed by $libdir.
>
> Why not? In order to ins
On Sat, 30 Jan 2010 11:06:02 -0500
Tom Lane wrote:
> Ivan Sergio Borgonovo writes:
> > ... I can't make install (provided it works as expected, I
> > didn't try yet) since I sincerely hope that my user doesn't have
> > write right on whatever is pointed by $libdir.
>
> Why not? In order to ins
Ivan Sergio Borgonovo writes:
> ... I can't make install (provided it works as expected, I didn't try
> yet) since I sincerely hope that my user doesn't have write right on
> whatever is pointed by $libdir.
Why not? In order to install a C function, you have to be superuser,
which means you alre
I finally put enough code together and it has some chance it could
work.
It's time to test it.
Now I'm going to test it quite frequently.
My code is written and compiled in my ~/.
Then it is moved through svn to a test box where it is compiled under
another version of postgres, but still it ends u
23 matches
Mail list logo
