[SQL] RE:Table corrupted and data lost (second time in one month!!)

Previously... >FATAL 1: Memory exhausted in AllocSetAlloc() >pqReadData() -- backend closed the channel unexpectedly. >This probably means the backend terminated abnormally >before or while processing the request. > >A table has been corrupted and i don't know why... >It's really hard to recover

Re: [SQL] Table corrupted and data lost (second time in one month!!)

Fernando, > A table has been corrupted and i don't know why... > It's really hard to recover the table, and last time i lost some data > ;-( > > Someone can help me to solve this problem ??? I don't want this table > corrupted anymore My first thought would be hardware problems. Have you

[SQL] Table corrupted and data lost (second time in one month!!)

This is the second time in this month FATAL 1: Memory exhausted in AllocSetAlloc() pqReadData() -- backend closed the channel unexpectedly. This probably means the backend terminated abnormally before or while processing the request. A table has been corrupted and i don't know why... It's

RE: [SQL] Timezone conversion

Hi Cedar, Does this help? select CURRENT_TIMESTAMP, CURRENT_TIMESTAMP + '90 days'; timestamp|?column? + 2001-04-24 12:57:56+01 | 2001-07-23 12:57:56+01 > > I also have a question.. How, for example, would I add 90

Re: [SQL] select ... for update in plpgsql

'select ... for update' needs to be inside a transaction. plpgsql cannot start or end transactions. 'begin' and 'end' are not transaction statements. (read the docs). -Cedar On Fri, 20 Apr 2001, Jie Liang wrote: > > Hi, > > I have a question about 'select ... for update'; > according to t

Re: [SQL] Timezone conversion

Umm.. define 'it'. (Isn't current_timestamp or now() already a timestamp?) select CURRENT_TIMESTAMP, CURRENT_TIMESTAMP-2*3600; timestamp| ?column? + 2001-04-24 13:06:11+03 | 1981-08-07 I also have a question.. How, for example, would I add