ns30966:~# NOTICE: Executing SQL: update tblPrintjobs set
ApplicationType = 1 where ApplicationType is null and
upper(DocumentName) like '%.DOC'
ns30966:~# NOTICE: Executing SQL: update tblPrintjobs set
ApplicationType = 1 where ApplicationType is null and
upper(DocumentName) like 'DOCUMENT%'
ns30966:~#
ns30966:~# ERROR: could not read block 3231 of relation
1663/165707259/173511769: Input/output error
CONTEXT: SQL statement "update tblPrintjobs set ApplicationType = 1
where ApplicationType is null and upper(DocumentName) like
'DOCUMENT%'"
PL/pgSQL function "fnapplicationtype" line 30 at execute statement
[1]+ Exit 1 psql -d kpmg -c "select
fnApplicationType()"
I get this error. Is this hardware related or could it be something
with the postgresql.conf settings.
I changed them for performance reasons. (More memory, more wal
buffers).
There are 2 databases. One got the error yesterday, I dropped it (was
brand new), recreated it and the error was gone.
Now the error is there again on another database.
Personally, I think it's a HD error.
Met vriendelijke groeten,
Bien à vous,
Kind regards,
<bold>Yves Vindevogel</bold>
<bold>Implements</bold>
<smaller>
</smaller>ns30966:~# NOTICE: Executing SQL: update tblPrintjobs set
ApplicationType = 1 where ApplicationType is null and
upper(DocumentName) like '%.DOC'
ns30966:~# NOTICE: Executing SQL: update tblPrintjobs set
ApplicationType = 1 where ApplicationType is null and
upper(DocumentName) like 'DOCUMENT%'
ns30966:~#
ns30966:~# ERROR: could not read block 3231 of relation
1663/165707259/173511769: Input/output error
CONTEXT: SQL statement "update tblPrintjobs set ApplicationType = 1
where ApplicationType is null and upper(DocumentName) like
'DOCUMENT%'"
PL/pgSQL function "fnapplicationtype" line 30 at execute statement
[1]+ Exit 1 psql -d kpmg -c "select
fnApplicationType()"
I get this error. Is this hardware related or could it be something
with the postgresql.conf settings.
I changed them for performance reasons. (More memory, more wal
buffers).
There are 2 databases. One got the error yesterday, I dropped it (was
brand new), recreated it and the error was gone.
Now the error is there again on another database.
Personally, I think it's a HD error.
Met vriendelijke groeten,
Bien à vous,
Kind regards,
Yves Vindevogel
Implements
<smaller>
Mail: yves.vindevogel@implements.be - Mobile: +32 (478) 80 82 91
Kempische Steenweg 206 - 3500 Hasselt - Tel-Fax: +32 (11) 43 55 76
Web: http://www.implements.be
<italic><x-tad-smaller>
First they ignore you. Then they laugh at you. Then they fight you.
Then you win.
Mahatma Ghandi.</x-tad-smaller></italic></smaller>
Mail: yves.vindevogel@implements.be - Mobile: +32 (478) 80 82 91
Kempische Steenweg 206 - 3500 Hasselt - Tel-Fax: +32 (11) 43 55 76
Web: http://www.implements.be
First they ignore you. Then they laugh at you. Then they fight you.
Then you win.
Mahatma Ghandi.