>Jeff Hoffmann wrote:
>
>> i've just gotten around to upgrading to 6.4 on a couple of FreeBSD
(2.2.7)
>> servers, and i'm having problems creating databases in alternate
locations.
>> basically, here's what i did:
>>
>> 1) dumped the data from a 6.3.2 install
>> 2) compiled 6.4 (completely generic
i've just gotten around to upgrading to 6.4 on a couple of FreeBSD (2.2.7)
servers, and i'm having problems creating databases in alternate locations.
basically, here's what i did:
1) dumped the data from a 6.3.2 install
2) compiled 6.4 (completely generically -- configure; make; make install)
3)
Bruce Momjian wrote:
>
> > Brook Milligan wrote:
> > >
> > >[jeroen@rulgfu sql]$ psql -f test.sql
> > >insert into testfile values (lo_import('test.sql'));
> > >ERROR: be_lo_import: can't open unix file"test.sql"
> > >
> > > Isn't the problem that the backend
Hi All!
Compiling Postgres-6.4 I came accross following option in ./configure
script:
" --enable-recode enable cyrillic recode support"
What is it for ? I wonder if it's intended to add capability of
translation between koi8 and win-1251 encofing, but I was unable to find
in manuals and
> After that, another programms, which was connected to postgres, loose
> connection.
> Regression test falls on PL/pgSQL.
This is what really has me stumped. The regression tests fail? I
wonder if I broke dynamic linking for bsdi 3.1. Check the regression
tests for other errors, like the LOAD
Bruce Momjian wrote:
> > >[jeroen@rulgfu sql]$ psql -f test.sql
> > >insert into testfile values (lo_import('test.sql'));
> > >ERROR: be_lo_import: can't open unix file"test.sql"
> > >
> > > Isn't the problem that the backend expects test.sql to be in the data
> In 6.4, it should work on all platforms. I know it works on bsdi 4.0.
Hello,
>
> What problems are you seeing.
I still have 3.1 :((
When I install plpgsql language, and prepare one test:
=>CREATE FUNCTION f_test () RETURNS abstime AS '
=>BEGIN
=>RETURN \'now\';
=>
> Brook Milligan wrote:
> >
> >[jeroen@rulgfu sql]$ psql -f test.sql
> >insert into testfile values (lo_import('test.sql'));
> >ERROR: be_lo_import: can't open unix file"test.sql"
> >
> > Isn't the problem that the backend expects test.sql to be in the data
>
> Bruce Momjian wrote:
> > > >[jeroen@rulgfu sql]$ psql -f test.sql
> > > >insert into testfile values (lo_import('test.sql'));
> > > >ERROR: be_lo_import: can't open unix file"test.sql"
> > > >
> > > > Isn't the problem that the backend expects test.sql to be
> Brook Milligan wrote:
> >
> >[jeroen@rulgfu sql]$ psql -f test.sql
> >insert into testfile values (lo_import('test.sql'));
> >ERROR: be_lo_import: can't open unix file"test.sql"
> >
> > Isn't the problem that the backend expects test.sql to be in the data
>
[Charset koi8-r unsupported, filtering to ASCII...]
> Hello,
> I've asked a question, about possibility of PL/pgSQL to work
> on OS BSDI-3.1. But I haven't got answer.(Thanx -Jose'-, now I know that it
> works
> on Linux !).
> But is there OS-oriented mailing list, where I can discuss my OS relate
On Fri, 13 Nov 1998, Postgres DBA wrote:
> Yeah, that's true, but you can simply overcome this problem with following
> query that you should issue right after "alter" query:
> update passwd set spamblock='TRUE';
Yea, I did that, but I guess what I'm looking for, was that when ever
anythi
Hello,
I've asked a question, about possibility of PL/pgSQL to work
on OS BSDI-3.1. But I haven't got answer.(Thanx -Jose'-, now I know that it
works
on Linux !).
But is there OS-oriented mailing list, where I can discuss my OS related
problems?
Thank you,
---
Sergei Chern
Brook Milligan wrote:
>
>[jeroen@rulgfu sql]$ psql -f test.sql
>insert into testfile values (lo_import('test.sql'));
>ERROR: be_lo_import: can't open unix file"test.sql"
>
> Isn't the problem that the backend expects test.sql to be in the data
> directories s
14 matches
Mail list logo
