Deniz Atak writes:
> thanks for your answer. Do you have any opinion about how can I find the
> corrupted rows? Do you know how to read:
> "could not read block 4707 of relation 1663/16384/16564"
You should read the chapter about Database Physical Storage in the
manual to find out how to interpr
On 1 Srpen 2011, 10:25, Deniz Atak wrote:
> Hi Deepak,
>
> thanks for your answer. Do you have any opinion about how can I find the
> corrupted rows? Do you know how to read:
>
> "could not read block 4707 of relation 1663/16384/16564"
>
> ?
> Also, there is one interesting thing: a very similar qu
On 1 Srpen 2011, 13:55, Deniz Atak wrote:
> Hi Thomas,
>
> thanks for your answer. We decided not to go further with this error,
> because soon we will have another product that replaces this one. Because
> I
> want to learn more about this topic, I did the following:
>
> Before I write your code,
Hi Deepak,
thanks for your answer. Do you have any opinion about how can I find the
corrupted rows? Do you know how to read:
"could not read block 4707 of relation 1663/16384/16564"
?
Also, there is one interesting thing: a very similar query like this:
select src_ip,round(sum(size)/175) from t
Hi Thomas,
thanks for your answer. We decided not to go further with this error,
because soon we will have another product that replaces this one. Because I
want to learn more about this topic, I did the following:
Before I write your code, I tried:
select oid,ctid,relname from pg_class where cti
On 1 Srpen 2011, 8:27, Deniz Atak wrote:
> Deepak, Tom thanks for answering.
>
> Tom, we have psql 8.1.18. So you are right, this weird message is because
> of
> the old version. I will check with my colleague about the possible
> reasons.
> What can I do if there is a messed up table?
First of al
I am not sure how big your table is one way we implemented here was we selected
the clean rows and outputted it to a csv file. And the rows affected we had to
load from the backup, luckily we had the clean backup.
Ex: assume you have 1,2,3,4,5100 rows and the corrupted is between 60-70. I
o
Deepak, Tom thanks for answering.
Tom, we have psql 8.1.18. So you are right, this weird message is because of
the old version. I will check with my colleague about the possible reasons.
What can I do if there is a messed up table?
Regards,
Deniz
On Sat, Jul 30, 2011 at 11:45 PM, Tom Lane wrote
Deniz Atak writes:
> I am using postgresql on Glassfish server and I have EJB 3.0 for ORM. I am
> trying to run a query in PSQL but receiving following error:
> Local Exception Stack:
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.0.0.v20091031-r5713): org.eclipse.persistence.
My guess is some one moved the data folder or the directory got deleted
(/var/lib/pgsql/9.0/data/.../...1663/16384/16564). Without server restart. I am
sure some experts gonna answer this very well.
Thanks
Deepak
On Jul 30, 2011, at 2:01 AM, Deniz Atak wrote:
> Hi,
>
> I am using postgresql
Hi,
I am using postgresql on Glassfish server and I have EJB 3.0 for ORM. I am
trying to run a query in PSQL but receiving following error:
Local Exception Stack:
Exception [EclipseLink-4002] (Eclipse Persistence Services -
2.0.0.v20091031-r5713): org.eclipse.persistence.exceptions.DatabaseExcept
11 matches
Mail list logo
