Strange problem with inserts.

Started by Manuel Durán Agueteabout 24 years ago2 messagesgeneral
Jump to latest
#1Manuel Durán Aguete
manuel.duran@quantumgap.com

Hi,

I'm usign PostgreSQL v7.1.2 under Solaris 7 + DBD::Pg for a project
degree. The project is about data adquisiction and process. In the last
days when a lot of data (10>-->20 rec/sec. is inserted the processes
that are reading gets records that not correspond with the statement
that are executing.

p.e:
The process 'A' reads data with type = A
SELECT * FROM data_collected where type = A order by id.

id is indexed.
Looking the logs the process 'A' process data with type 'B' or 'C' or
'D' and of course "A".

Any Idea?

Thanks.

#2Oliver Elphick
olly@lfix.co.uk
In reply to: Manuel Durán Aguete (#1)
Re: Strange problem with inserts.

On Thu, 2002-02-14 at 10:29, Manuel Duran Aguete wrote:

Hi,

I'm usign PostgreSQL v7.1.2 under Solaris 7 + DBD::Pg for a project
degree. The project is about data adquisiction and process. In the last
days when a lot of data (10>-->20 rec/sec. is inserted the processes
that are reading gets records that not correspond with the statement
that are executing.

p.e:
The process 'A' reads data with type = A
SELECT * FROM data_collected where type = A order by id.

id is indexed.
Looking the logs the process 'A' process data with type 'B' or 'C' or
'D' and of course "A".

The type field looks like a char(1) so a value to test against it should
be quoted:
SELECT * FROM data_collected where type = 'A' order by id

As you present it, your query will look for a column called "a" and
compare "type" to "a" for each row. If there is no column "a", I have
no idea what else might be wrong.

--
Oliver Elphick Oliver.Elphick@lfix.co.uk
Isle of Wight http://www.lfix.co.uk/oliver
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C

"My sheep hear my voice, and I know them, and they
follow me; And I give unto them eternal life; and they
shall never perish, neither shall any man pluck them
out of my hand." John 10:27,28