2009/11/16 Tom Lane :
> Alvaro Herrera writes:
>> Magnus Hagander wrote:
>>> Which leads to the question - do we want to back out the
>>> patch, have 8.2 keep working on that, and having 8.2 fail in the few
>>> unusual scenarios we have now, or do we also backpatch the requirement
>>> to run on wi
The following bug has been logged online:
Bug reference: 5200
Logged by: Andrew Masterton
Email address: a.j.master...@open.ac.uk
PostgreSQL version: 8.3.8
Operating system: RedHat Enterprise 5.4
Description:Use of min suffix in autovacuum_naptime ignored
Details:
T
On Thu, Nov 19, 2009 at 1:03 PM, Orange wrote:
>
> Hi it shows like you see bellow
>
> The stange that once I copy it to other file it shows right
>
and this is related to postgres... because...
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Heikki Linnakangas writes:
> Try without the parenthesis in OVER:
> ...
> I'm quite surprised by the error message that produces, though...
It's actually correct: the syntax with parens specifies copying
and modifying the named WINDOW definition, but you're not allowed to
copy-and-modify a defini
Hi it shows like you see bellow
The stange that once I copy it to other file it shows right
Best wishes
Boris Fain
<>
Iliya Krapchatov wrote:
> select first_value( pk ) OVER ( pkw ) FROM t
> WINDOW pkw AS ( PARTITION BY pk ORDER BY pk RANGE BETWEEN UNBOUNDED
> PRECEDING AND UNBOUNDED FOLLOWING );
>
> I see following lines in response:
> ---
> ERROR: cannot override frame clause of window "pkw"
> LINE 1: select f
Valaki Valahol wrote:
> ERROR: relation with OID 28461 does not exist
http://wiki.postgresql.org/wiki/FAQ#Why_do_I_get_.22relation_with_OID_.23.23.23.23.23_does_not_exist.22_errors_when_accessing_temporary_tables_in_PL.2FPgSQL_functions.3F
Upgrading to 8.4 (or 8.3) should fix that.
--
Heikki
Hello
You cannot to drop temporary table in stored procedure. Then you can
have a problem. There are two possibilities: a) you will upgrade to
8.3, b) you will change code - minimum is replace drop table by
truncate table
please, read
http://www.postgres.cz/index.php/Automatic_execution_plan_cach
The following bug has been logged online:
Bug reference: 5199
Logged by: Iliya Krapchatov
Email address: my_work...@inbox.ru
PostgreSQL version: 8.4.1
Operating system: Windows XP
Description:Window frame clause wrong (?) behaviour
Details:
I am new at WINDOW clause
Dear Sirs,
My name is Zoltán Ötvös and I'm from Hungary.
Im using PostgreSQL database server from many years and I'm very satisfied with
this
database.
I'm wanted to write a little financial routine in Linux under Lazarus but for
the first I've
tested it under pgAdmin. Because I didn't wanted
"Lyamin Mikhail" writes:
> 1) create table
> 2) create inherited table
> 3) add fields in parent table
> 4) add fields in child table
> 5) make dump
> Now you have wrong order of fields in insert.
AFAIK this will happen only if you use the --inserts switch, which is
deprecated for exactly this r
Hi,
for csv output, we have a 750 Mo logfile. But on another site, we have
an logfile of 1,6 Go and logger process was using more than 3 Go of
RAM.
Even with our configuration (log collector, silent mode and
csv/stderr), we launched potsgresql daemon like this :
pg_ctl -l ${HOME}/pgsql/logs/postg
The following bug has been logged online:
Bug reference: 5198
Logged by: Lyamin Mikhail
Email address: lma...@gmail.com
PostgreSQL version: 8.3.8
Operating system: Debian
Description:Plain dump: wrong field order for inherited tables
Details:
pg_dump - version 4.8.1
goldenhawking wrote:
The following bug has been logged online:
Bug reference: 5194
Logged by: goldenhawking
Email address: goldenhawk...@vip.163.com
PostgreSQL version: 8.4.1
Operating system: Ubuntu 9.10 accessed by Vista Home basic
Description:fire IDispatch Error
14 matches
Mail list logo
