Sir,
The base table is having bytea and having records around 32 lakhs shows size
of 300 mb.
bytea field has attached documents size is not shown in the base table.
The message on Tomcat is
--begin text --
4 Jun, 2014 3:29:07 PM org.apache.catalina.core.StandardWrapperValve invoke
INFO: WARN [TP-Processor24] JDBCExceptionReporter.logExceptions(100) | SQL
Error: 0, SQLState: 42P01
ERROR [TP-Processor24] JDBCExceptionReporter.logExceptions(101) | ERROR:
relation "public.file_attachments" does not exist
Position: 238
org.hibernate.exception.SQLGrammarException: could not execute query
at
org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:90)
at
org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
at org.hibernate.loader.Loader.doList(Loader.java:2231)
at
org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2125)
at org.hibernate.loader.Loader.list(Loader.java:2120)
at
org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:118)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1596)
at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:306)
at
org.hibernate.impl.CriteriaImpl.uniqueResult(CriteriaImpl.java:328)
at
com.nic.edistrict.certificates.dao.impl.FileAttachmentsDaoImpl.getFileAttachments(FileAttachmentsDaoImpl.java:53)
at
com.nic.edistrict.certificates.service.impl.FileAttachmentsManagerImpl.getFileAttachments(FileAttachmentsManagerImpl.java:28)
at sun.reflect.GeneratedMethodAccessor1999.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:28
--end text
Even though table is present and connections are opening for subsequently.
The message
appear at frequent intervals. Is there any way to see the complete size of
a table
which has bytea filed like database
pg_size_pretty(pg_relation_size('file_attachments') shows
just 300 mb.
Any help is welcome.
Regards
Ramachandran s
--
View this message in context: http://postgresql.1045698.n5.nabble.com/bytea-Issue-Reg-tp5805838p5806146.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
