Alexandra Nitzschke <[EMAIL PROTECTED]> writes:
> This monday I updated postgres to 8.3.5 on the standby server.
> After that I intialized the database
> ( copy once the database from the primary system: removing data/* on stand-by,
> setting the database on primary in backup-modus and then copy t
"Rod Taylor" <[EMAIL PROTECTED]> writes:
> That was the short form exhibiting the bug. Selecting the complex
> column from a table into a value results in the same error.
Well, you could do "SELECT t.* INTO v_time". The fundamental point here
is that when the INTO target is a rowtype variable, pl
"Rod Taylor" <[EMAIL PROTECTED]> writes:
> DECLARE
> v_time timestamp_with_precision;
> BEGIN
> SELECT (CURRENT_DATE, 'day')::timestamp_with_precision
> INTO v_time;
You're overthinking the problem, it should just read
SELECT CURRENT_DATE, 'day'
INTO v_time;
The following bug has been logged online:
Bug reference: 4533
Logged by: Rod Taylor
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.5
Operating system: FreeBSD 7.0 Stable
Description:Plpgsql complex type failure
Details:
The below script should be able to c
