[GENERAL] OFFTOPIC: core dumped with strcpy,atoi,sprintf.

2012-09-14 Thread Ing.Edmundo.Robles.Lopez
Hi. I hope you can help me. I have problems with some functions like strcpy, atoi, etc and would like to know the correct list where I have to ask this: I have compiled a program under SCO Openserver, and run succesfully. But when i compile the same program in Ubuntu 12.04, i got a co

[GENERAL] Which postgresql should i choose to migrate from 8.3 ? 8.4 or 9.1?

2012-08-28 Thread Ing.Edmundo.Robles.Lopez
Hi! We are using postgresql 8.3 in my work, and the need to migrate to a newer version became urgent :) I've been reading the release notes for versions 8.4 and 9.1, but is not clear to me which problems I can have with version 8.4 or 9.1 from a dump 8.3 My boss thinks we would have fewer p

Re: [GENERAL] REINDEX and COPY is wainting since Jun 21!

2012-07-27 Thread Ing.Edmundo.Robles.Lopez
El 27/07/2012 12:26 p.m., Alan Hodgson escribió: On Friday, July 27, 2012 11:59:49 AM Ing.Edmundo.Robles.Lopez wrote: Hi, i have postgres 8.3 running in SCO Openserver 5.0.7 today, i had problems to start psql, the error mesage was: 'FATAL Memory out, Detail: Failed on resqueted

Re: [GENERAL] REINDEX and COPY is wainting since Jun 21!

2012-07-27 Thread Ing.Edmundo.Robles.Lopez
thanks a lot for answer. El 27/07/2012 12:26 p.m., Alan Hodgson escribió: On Friday, July 27, 2012 11:59:49 AM Ing.Edmundo.Robles.Lopez wrote: Hi, i have postgres 8.3 running in SCO Openserver 5.0.7 today, i had problems to start psql, the error mesage was: 'FATAL Memory out, Detail: F

[GENERAL] REINDEX and COPY is wainting since Jun 21!

2012-07-27 Thread Ing.Edmundo.Robles.Lopez
Hi, i have postgres 8.3 running in SCO Openserver 5.0.7 today, i had problems to start psql, the error mesage was: 'FATAL Memory out, Detail: Failed on resqueted size ...' , and after i checked the process i noticed the following: the elder REINDEX had been running since Jun-21 by 3

Re: [GENERAL] weird negative seconds on checkpoint message.

2011-12-02 Thread Ing.Edmundo.Robles.Lopez
El 02/12/2011 04:50 p.m., Adrian Klaver escribió: On Friday, December 02, 2011 2:33:05 pm Ing.Edmundo.Robles.Lopez wrote: Hi! I have the next messege: LOG: checkpoints are occurring too frequently (-21093 seconds apart) Postgres 8.3.11 is running on SCO Openserver 5.0.7 and this is my

[GENERAL] weird negative seconds on checkpoint message.

2011-12-02 Thread Ing.Edmundo.Robles.Lopez
Hi! I have the next messege: LOG: checkpoints are occurring too frequently (-21093 seconds apart) Postgres 8.3.11 is running on SCO Openserver 5.0.7 and this is my checkpoint configuration: # - Checkpoints - checkpoint_segments = 32# in logfile segments, min 1, 16MB each checkpoint_ti

[GENERAL] Why fetch a row is more slow than a 'selec * from'

2011-11-07 Thread Ing.Edmundo.Robles.Lopez
Hello I've been looking for ways to optimize a query. I have a table with 120,000 records. When searched on: select * from big_table takes to run: 3 min. I wanted to use cursors and the query with big_table, it taked 11 minutes. It caught my attention on a small_table (100 records) becaus

[GENERAL] psql is too slow to connect

2011-11-04 Thread Ing.Edmundo.Robles.Lopez
Hi, I have a problem with psql, is very slow to connect. I Checked the status of my network and the server and the client respond ok. Any other ideas? Perhaps, should i need review, connections, shared memory, or if a big table is being accessed?? El contenido de este correo electrónico y

[GENERAL] Getting X coordinate from a point(lseg), btw i read the man page about points.

2011-10-27 Thread Ing.Edmundo.Robles.Lopez
Hi in the main page about geometric operations said: It is possible to access the two component numbers of a point as though it were an array with indices 0 and 1. For example, if t.p is a point column then SELECT p[0] FROM t retrieves the X coordinate and UPDATE t SET p[1] = ... cha

[GENERAL] How are PGRES_FATAL_ERROR raised?????

2011-10-27 Thread Ing.Edmundo.Robles.Lopez
Hi! I would like toknow the conditionsorreasons where postgressends aPGRES_FATAL_ERROR. El contenido de este correo electrónico y sus archivos adjuntos son privados y confidenciales y va dirigido exclusivamente a su destinatario. No se autoriza la utilización, retransmisión, diseminación, o