Hello everyone,
It is the second time i got this error message (sorry, its french, i
prefer to c/p this one than making a bad translation) :
---88---8---
pg_dump: ERREUR: Impossible d'accéder au statut de la transaction
892415538
DETAIL: Impossible d'ouvrir le
Alvaro Herrera wrote:
Froggy / Froggy Corp. wrote:
Hello everyone,
It is the second time i got this error message (sorry, its french, i
prefer to c/p this one than making a bad translation) :
---88---8---
pg_dump: ERREUR: Impossible d'accéder
Alvaro Herrera wrote:
Froggy / Froggy Corp. wrote:
Alvaro Herrera wrote:
Froggy / Froggy Corp. wrote:
Hello everyone,
It is the second time i got this error message (sorry, its french, i
prefer to c/p this one than making a bad translation) :
---8
Hello,
I got some problem on trigger which call them self for UPDATE
BEFORE/AFTER.
Here is some test :
The UPDATE test function/table :
--888--
CREATE SEQUENCE id_my_table_seq;
CREATE table my_table (
id_my_table int4
Tom Lane wrote:
Froggy / Froggy Corp. [EMAIL PROTECTED] writes:
PG7 dont make recursiv, it wait for the end of the trigger BEFORE_UPDATE
to call the new UPDATE stat and forgot the 3rd AFTER_UPDATE. PG8 is
better, it call trigger like real recursiv fonction, but allways dismiss
the 3rd
Its my plan in fact, it was to make some optimisation, because i need to
copy all the test from the BEFORE statement to the AFTER.
Thx for your help,
Regards,
Tom Lane wrote:
Froggy / Froggy Corp. [EMAIL PROTECTED] writes:
Tom Lane wrote:
This is a really badly designed trigger anyway
Hi everyone,
I made a tetris under pl/pgsql and i encounter some problem with this
non commun use of pl/pgsql. For each problem, i didn't see information
about them, so my report :
- Array problem (7.4.7 8.0.1) :
I got a lot of problem with using array, like i saw under the ML,
Dénouement :
J'ai enfin trouvé toutes les réponses à mes questions via la comande
REINDEX.
Merci à Jean-Christophe Arnu (s'il passe par ici) qui a confirmé via
son article sur http://www.postgresqlfr.org/?q=node/view/49 la solution
que j'avais cherché depuis quelques temps.
Froggy / Froggy Corp
---BeginMessage---
Il me parait un peu illusoire de contester un test alors que CleverAge a
pris la peine de contacter la communauté francophone de PostgreSQL et que
personne ne s'est déplacée (pour des raisons que je ne critique pas).
Donc à partir de ce moment là, je trouve abhérant de
Hello,
In fact the problem seems to come from the INSERT INTO. I delete
everything from the function and only keep the INSERT INTO and get the
same problem.
Thx in advance for answers,
regards,
Stephan Szabo wrote:
On Tue, 20 Apr 2004, Froggy / Froggy Corp. wrote:
I try
Hello everyone,
I try to see if i can make a recursive function with a trigger set on
INSERT and doing an insert under my trigger function.
So i wrote a test function :
CREATE OR REPLACE FUNCTION testfunc() RETURNS SETOF RECORD AS '
DECLARE
use_t RECORD;
BEGIN
Hello,
I'am using postgresql to make different web site with differente
database for each, but with same table/link/...
So, i change from 7.2 to 7.4 and try to use template function to create
each new DB more easier (with user posgres):
CREATE DATABASE myowntemplate
Hello (again),
I read some documentation about tuning postgresql.conf but i didn't
find information clearly about how to use GeQo. It seems to help planner
but using a lot of CPU, and is usefull only for big join.
Per default, geqo = true, but in which case, geqo is usefull and in
Hello,
I asked one time for more benchmark soft to know where is the cpu
average, and read the post about optimising the postgresql.conf (and use
them), but i allways get a load 1 on fire time (dunno the right name,
coup de feu in french (10h00 - 14h00, 18h00 - 21h00).
For
14 matches
Mail list logo
