Victor Hugo dos Santos writes:
> On Tue, Jan 4, 2011 at 1:05 PM, Tom Lane wrote:
>> It looks like a corrupted-data problem from here. You need to isolate
>> and delete the bad row(s).
> # su - postgres -c "psql bacula -c 'SELECT md5 from public.file OFFSET
> 1417610 LIMIT 1'"
> server closed th
On Tue, Jan 4, 2011 at 1:05 PM, Tom Lane wrote:
> Victor Hugo dos Santos writes:
>> any idea ???
>
> It looks like a corrupted-data problem from here. You need to isolate
> and delete the bad row(s).
Hello again...
this is very, very strange !! :D
(sorry for long message, but I'm trying to sen
On Tue, 04 Jan 2011 11:04:56 -0600, Dan Sabin
wrote:
The two options are to give them a query tool we design so we can
restrict their actions (to prevent the database from being screwed up).
If their user still has access to doing other things it might be possible
for that data to be mod
Dan Sabin wrote:
> In order to do this the client needs an interface to access the
> database. The two options are to give them a query tool we design
> so we can restrict their actions (to prevent the database from
> being screwed up). The other option would be to restrict their
> access in the
Hello,
So I plan on deploying a Postgres DB in an military project. On our admin end
we are using the tool to help set up the database for delivery. Now the problem
comes once the system is delivered. The database is used to record all the
system messages for easy retrieval. This feature is rar
On Tue, Jan 4, 2011 at 1:05 PM, Tom Lane wrote:
> Victor Hugo dos Santos writes:
>> any idea ???
>
> It looks like a corrupted-data problem from here. You need to isolate
> and delete the bad row(s).
hello
any sugestion about how found and delete the bad row(s) ??
thanks
--
--
Victor Hugo
Victor Hugo dos Santos writes:
> any idea ???
It looks like a corrupted-data problem from here. You need to isolate
and delete the bad row(s).
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http
On Tue, Jan 4, 2011 at 12:02 PM, Victor Hugo dos Santos
wrote:
[...]
> but, I'm dowloading the 64bit image now and after I install it in a
> Virtual Machine to try.
I'm a stupid !! :(
I can't restore the same DB from 32bit in 64bits !!!
for this, should be export first in 32bits (pg_dump) and a
On Tue, Jan 4, 2011 at 11:07 AM, Thomas Markus wrote:
> hi,
>
> looks like a 32bit version so 4294967293 is too much (4GB). Use a 64bit
> version
.. is a small table (look the size of last dump)
=
$ ls -lh /tmp/public-files.sql
-rw-r- 1 root root 298M Jan 4 11:59 /tmp/public
hi,
looks like a 32bit version so 4294967293 is too much (4GB). Use a 64bit
version
regards
Thomas
Am 04.01.2011 14:48, schrieb Victor Hugo dos Santos:
Hello,
Actually I use postgresql version 8.4.6-0ubuntu10.04 in bacula server
to save information about backups from bacula.
But, 2 days a
Run ulimit -a and verify the max memory size allowed for the postgres
account.(I assume you are running postmaster under the postgres account,
right?) The allowed size should be large enough for the postmaster plus shared
buffers and several other GUCs that require memory.
Bob Lunney
--- O
Run ulimit -a and verify the max memory size allowed for the postgres
account.(I assume you are running postmaster under the postgres account,
right?) The allowed size should be large enough for the postmaster plus shared
buffers and several other GUCs that require memory.
Bob Lunney
--- O
Run ulimit -a and verify the max memory size allowed for the postgres
account.(I assume you are running postmaster under the postgres account,
right?) The allowed size should be large enough for the postmaster plus shared
buffers and several other GUCs that require memory.
Bob Lunney
--- O
On Tue, Jan 4, 2011 at 10:59 AM, Bob Lunney wrote:
> Run ulimit -a and verify the max memory size allowed for the postgres
> account.(I assume you are running postmaster under the postgres account,
> right?) The allowed size should be large enough for the postmaster plus
> shared buffers and s
Hello,
Actually I use postgresql version 8.4.6-0ubuntu10.04 in bacula server
to save information about backups from bacula.
But, 2 days ago, the postgresql make a error when I run the command
pg_dump. This is the error:
02-Jan 06:32 bacula-dir JobId 31005: BeforeJob: pg_dump
Στις Wednesday 29 December 2010 16:06:41 ο/η Achilleas Mantzios έγραψε:
> Hello,
> i noticed that the user name as displayed in the postgresql log (specified by
> %u) in the log_line_prefix
> does not show the user name of the effective user (current_user)as set by
> "SET SESSION AUTHORIZATION"
16 matches
Mail list logo
