Hello community,
we are running a CRM system with Postgres database (version 8.3). To
organize handwritten contracts we save them scanned as LOBs. Normally
they are unlinked in case of deleting them. However we run a cron job
which does vacuumlo to get save that there is nothing in the nirvana
Alexander Strotmann a écrit :
> [...]
> we are running a CRM system with Postgres database (version 8.3). To
> organize handwritten contracts we save them scanned as LOBs. Normally
> they are unlinked in case of deleting them. However we run a cron job
> which does vacuumlo to get save that there i
I am dumping postgres 7 tables under the postgres account mydb# pg_dump -O
-a -t mytable > mytable.out and am getting either
empty dumps ( actual db tables are populated) or no dump at all.
I have file write permissions and this process has worked in the past.
Any suggestions what might be wrong?
On Sun, Nov 2, 2008 at 4:29 PM, Daniel Punton <[EMAIL PROTECTED]> wrote:
> I am dumping postgres 7 tables under the postgres account mydb# pg_dump -O
> -a -t mytable > mytable.out and am getting either
> empty dumps ( actual db tables are populated) or no dump at all.
> I have file write permissio
Hello,
OS: Windows 2003 64bits
Cpu : 2x Opteron Dual core
Ram : 8Go Ram
Disk : Areca Raid10 6x 200Go sata
Postgresql 8.3.4
we're experiencing problems since some weeks with always the same
error (same transaction 0 and same pg_clog file ) :
2008-10-31 20:14:27 CET 10.0.0.119 exile PANIC: co
