[GENERAL] Error: index of catalog table

ROR: cannot open segment 1 of relation pg_proc_prosrc_index What can I do? I know... i can recreate my db... hummm... :) any suggestion more? TIA Rober -- Roberto Moreda Resp. Dpto. Informática Handem/San Luis Tlf +34 981 779000 Fax +34 981 779022 Pol. Piadela Sur, Autovía A6 Sal.567 15

[GENERAL] FATAL 1: my bits moved right off the end of the world!

When I try to CREATE a FUNCTION I got this message in the debug log : FATAL 1: my bits moved right off the end of the world! Any advice? TIA Roberto -- Roberto Moreda Resp. Dpto. Informática Handem/San Luis Tlf +34 981 779000 Fax +34 981 779022 Pol. Piadela Sur, Autovía A6 Sal.567

[GENERAL] Two questions about join performance

g='N'. I'm in a big trouble because of all this. TIA again. Roberto -- Roberto Moreda Resp. Dpto. Informática Handem/San Luis Tlf +34 981 779000 Fax +34 981 779022 Pol. Piadela Sur, Autovía A6 Sal.567 15300 Betanzos (A Coruña) - España

[GENERAL] eqsel ?

I'm digging into obtain the way to explicit the use of index in a where clause and I found that the proc eqsel can help me... ? Any clue? TIA Roberto -- Roberto Moreda Resp. Dpto. Informática Handem/San Luis Tlf +34 981 779000 Fax +34 981 779022 Pol. Piadela Sur, Autovía A6 Sa

[GENERAL] Slow joins

alue = 10 rows over the 7). Postgres does a Seq Scan. How can I speed up that scan? How can I force the use of the index? Where can I found general recomendations to speed up queries? TIA Roberto -- Roberto Moreda Resp. Dpto. Informática Handem/San Luis Tlf +34 981 779000 Fax +34

[GENERAL] Transations in postgres

Rober -- Roberto Moreda Resp. Dpto. Informática Handem/San Luis Tlf +34 981 779000 Fax +34 981 779022 Pol. Piadela Sur, Autovía A6 Sal.567 15300 Betanzos (A Coruña) - España