Hey all, I posted this over on the EDB forums as well, no answers yet, so I
am trying here.
I am trying to set up a pg_dump between a postgresql 8.3.1 server and edb
8.3 server.
This is to get slony working between the two.
When I do:
pg_dump -s -U testmaster -h 10.0.0.1 -p 5444 testuser | psql
Hi,
I'm currently testing a 25G Postgres 8.3.0 database on Apple Xserve/
Intel with Mac OSX 10.5 (Leopard).
There are two identical machines with identical configurations (hw
and sw).
Running a pg_restore of a binary backup file (3.8 GB) on both
machines gives the following results:
On Wed, Jun 04, 2008 at 11:43:24AM +0200, Rudolf van der Leeden wrote:
I'm currently testing a 25G Postgres 8.3.0 database on Apple Xserve/
Intel with Mac OSX 10.5 (Leopard).
There are two identical machines with identical configurations (hw
and sw).
Running a pg_restore of a binary
Hi,
I'm writing some paper about instance recovery and I'm wondering how
PostgreSQL act when find a corrupted archived WAL during the restore
command.
I found that when instance recovery starts the zero_damaged_pages is
set to true.
This parameter affect only data files with corrupted pages or
As in the title - is it possible to convert WAL for another architecture?
(source database on Linux/i386, contemplating chances to restore
backup on Linux/amd64)
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
Mikel Lindsaar [EMAIL PROTECTED] writes:
I am trying to set up a pg_dump between a postgresql 8.3.1 server and edb
8.3 server.
When I do:
pg_dump -s -U testmaster -h 10.0.0.1 -p 5444 testuser | psql -U postgres -h
localhost testslave
I get:
pg_dump: SQL command failed
pg_dump: Error
Rudolf van der Leeden [EMAIL PROTECTED] writes:
[ different times to build a varchar index on allegedly identical
installations ]
Perhaps one is using C locale and the other is not? strcmp() vs
strcoll() is a pretty big hit. In general it'd be worth dumping
out the whole contents of
Hi,
I'd like to use postgres to store my secret data in a way that only
me (the DBA, owner of the table) can access the talbe while the root
(system administrator) who installed and maintains the server - will
not be able to see the data.
Now, I think that db authentication is simply not enough
On Mon, Jun 2, 2008 at 6:16 PM, [EMAIL PROTECTED] wrote:
Is there a way to protect the data files, so even the malicious
administrator cannot see the data ?
Encrypt it. Though, how you store the key will be important.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
On Mon, Jun 02, 2008 at 03:16:54PM -0700, [EMAIL PROTECTED] wrote:
I'd like to use postgres to store my secret data in a way that only
me (the DBA, owner of the table) can access the talbe while the root
(system administrator) who installed and maintains the server - will
not be able to see
Now, I think that db authentication is simply not enough , because
the administrator can copy the data files to his own machine (where he
is the owner of the database).
Or just change pg_hba.conf to his taste
Is there a way to protect the data files, so even the malicious
administrator
[EMAIL PROTECTED] writes:
I'd like to use postgres to store my secret data in a way that only
me (the DBA, owner of the table) can access the talbe while the root
(system administrator) who installed and maintains the server - will
not be able to see the data.
If you think you can hide
Has anyone dealt with the issue of using tsearch2 with statute cites
yet? Do you have a sample dictionary or any tips? We need to confirm
with the users, but I think desired behavior is that a statute cite of
'813.12(1)(am)' should be found on any leading portions -- that is,
any of the
Kevin,
in 8.4 it'd be possible to use prefix search, see our presentation
about GIN at PGCon 2008. For now you can use dict_regexp, which
allows to use perl's regular expressions. Get it from
http://vo.astronet.ru/arxiv/dict_regex.html
Oleg
On Wed, 4 Jun 2008, Kevin Grittner wrote:
Has
I am trying to run commands from the shell (without becoming the postgres user
first), which work fine on our live server, but on our dev server I receive
FATAL authentication errors.
[EMAIL PROTECTED] tmp]$ createdb -U postgres lan_portal
createdb: could not connect to database postgres:
Marc Fromm [EMAIL PROTECTED] writes:
I am trying to run commands from the shell (without becoming the postgres
user first), which work fine on our live server, but on our dev server I
receive FATAL authentication errors.
[EMAIL PROTECTED] tmp]$ createdb -U postgres lan_portal
createdb:
16 matches
Mail list logo