"Dan Langille" <[EMAIL PROTECTED]> writes:
> Is there a correct way to replace such definitions? I tried just a drop
> function and then a create function, but:
> ERROR: fmgr_info: function 16557: cache lookup failed
CREATE OR REPLACE FUNCTION (new in 7.2) would do the trick.
On 23 Feb 2002 at 16:06, Tom Lane wrote:
> Actually, under 7.2 the preferred definition is just
>
> CREATE FUNCTION "plpgsql_call_handler" () RETURNS opaque AS
> 'plpgsql', 'plpgsql_call_handler' LANGUAGE 'C';
Is there a correct way to replace such definitions? I tried just a drop
function an
>> [1] - the change I made: this
>>
>> CREATE FUNCTION "plpgsql_call_handler" () RETURNS opaque AS
>> '/usr/local/lib/plpgsql.so', 'plpgsql_call_handler' LANGUAGE 'C';
>>
>> became
>>
>> CREATE FUNCTION "plpgsql_call_handler" () RETURNS opaque AS
>> '/usr/local/lib/postgresql/plpgsql.so', 'plpg
On 23 Feb 2002 at 12:18, Sean Chittenden wrote:
> Real quick, FreeBSD is currently building with MIT kerberos support
> out of the box. Are there any plans to merge in the Heimdal kerberos
> patches? -sc
I don't know. I just asked around on IRC... I guess everyone is watching
the Belarus/Rus
> [1] - the change I made: this
>
> CREATE FUNCTION "plpgsql_call_handler" () RETURNS opaque AS
> '/usr/local/lib/plpgsql.so', 'plpgsql_call_handler' LANGUAGE 'C';
>
> became
>
> CREATE FUNCTION "plpgsql_call_handler" () RETURNS opaque AS
> '/usr/local/lib/postgresql/plpgsql.so'
On 23 Feb 2002 at 14:50, Tom Lane wrote:
> "Dan Langille" <[EMAIL PROTECTED]> writes:
> > now I'm getting: ERROR: SearchSysCache: Bad cache id 27
>
> I believe we've seen this from trying to load a 7.1 plpgsql.so
> into 7.2.
Tom! Well done. Thank you. That was the problem.[1] After correcti
> Sean: you are on the same track I am. Yes, I found 9 such values in a
> timestamp field. I corrected the data, exported, and imported into 7.2.
> All went well[1].
>
> Now my concern is how the value 'current' found its way into a timestamp
> field I'm looking at the application.
I
"Dan Langille" <[EMAIL PROTECTED]> writes:
> now I'm getting: ERROR: SearchSysCache: Bad cache id 27
I believe we've seen this from trying to load a 7.1 plpgsql.so
into 7.2.
regards, tom lane
---(end of broadcast)---
TIP 6
On 23 Feb 2002 at 14:28, Dan Langille wrote:
> On 23 Feb 2002 at 11:22, Sean Chittenden wrote:
>
> > > I've just been able to confirm that 7.1.2 can import the above data. My
> > > plans for 7.2 are now on hold while I try to find a way to get 7.2 to
> > > accept the data that has been exported
On 23 Feb 2002 at 11:22, Sean Chittenden wrote:
> > I've just been able to confirm that 7.1.2 can import the above data. My
> > plans for 7.2 are now on hold while I try to find a way to get 7.2 to
> > accept the data that has been exported from 7.1.
>
> perl -p -i -e 's#current#now#igo' pgsql_
> I've just been able to confirm that 7.1.2 can import the above data. My
> plans for 7.2 are now on hold while I try to find a way to get 7.2 to
> accept the data that has been exported from 7.1.
perl -p -i -e 's#current#now#igo' pgsql_dump.sql
Double check that you don't have the word 'curr
Dan Langille writes:
> > * The date/time value 'current' is no longer available. You will need
> > to
> >rewrite your applications.
>
> Thank you. This isn't an application.
If it isn't, then what do you need the data for? ;-)
> It is data dumped from 7.1.2. How are we to u
On 23 Feb 2002 at 0:59, Dan Langille wrote:
> I'm importing the data from my 7.1.2 database into 7.2 and I've found a few
> problems.
[snip]
> $ psql fp2migration < fp2migration.sql.timestamp.library
> [snip]
> ERROR: copy: line 2537, Bad timestamp external representation 'current'
> lost sync
On 23 Feb 2002 at 12:19, Peter Eisentraut wrote:
> Dan Langille writes:
>
> > $ psql fp2migration < fp2migration.sql.timestamp.library
> > [snip]
> > ERROR: copy: line 2537, Bad timestamp external representation 'current'
> > lost synchronization with server, resetting connection ^C
> >
> > Any
Dan Langille writes:
> $ psql fp2migration < fp2migration.sql.timestamp.library
> [snip]
> ERROR: copy: line 2537, Bad timestamp external representation 'current'
> lost synchronization with server, resetting connection
> ^C
>
> Any clues as to what will fix this problem?
Quoth the release note
I'm importing the data from my 7.1.2 database into 7.2 and I've found
a few problems.
The first one was:
ERROR: Bad timestamp external representation 'current_timestamp'
I fixed that problem by removing the quotes within the input data.
The next problem seems slightly harder to fix.
$ psql
16 matches
Mail list logo
