I have a standard Redhat 9 installation with the
exception of upgrading bison to bison-1.875-7.1
I can build the postgres rpm files from the source
for version 7.4.5 no problems with the following command:
rpmbuild --rebuild --define 'build89 1' --define
'python 0' --define 'test 0' --defi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
A workaround is symlinking /usr/lib/kerberos/* to /usr.
We are aware of that and 7.4.7 will ship with that change.
Regards,
On Mon, 31 Jan 2005, Donald Fraser wrote:
I have a standard Redhat 9 installation with the exception of upgrading bison
to b
Devrim GUNDUZ wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
A workaround is symlinking /usr/lib/kerberos/* to /usr.
We are aware of that and 7.4.7 will ship with that change.
Hmm, guess I need to patch my SPEC file.
--
Until later, Geoffrey
---(end of broadcast)--
I'm seeing the following with one of our tables:
db=> select * from diskmon.vob_usage;
ERROR: _mdfd_getrelnfd: cannot open relation vob_usage: No such file or
directory
This is running under 7.3.3. I'm not sure how this occurred. Is this table
completely trashed or is there something that
Operating System: Fedora core 1
From: postgresql 7.2 database
To: postgresql 7.3 database
I'm trying to restore a tar dump of postgresql 7.2 databases into a 7.3
server. I have two databases (db1,db2) both containing binary data. The
tar was dumped with the following command:
pg_dump -C
Ben Kim <[EMAIL PROTECTED]> writes:
> I'm trying to restore a tar dump of postgresql 7.2 databases into a 7.3
> server. I have two databases (db1,db2) both containing binary data. The
> tar was dumped with the following command:
> pg_dump -C -b -F t -i db1.tar db1
> The first one was restor
__Do You Yahoo!?Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Thanks for the prompt help. The problem seems to be missing users.
Removing -C revealed the problem.
> Other than that, though, the only thought that comes to mind is that you
> may be confused about the use of -C. IIRC, specifying it at dump time
> is useless --- it needs to be given to pg_rest
Any help that you could give would be greatly appreciated.
I’m running PostgreSQL 8.0 on Windows 2003.
When I attempt to connect to the database using Access and ODBC
from a Windows 2000 host I get:
“Could
not connect to remote socket”
I believe that this problem is
Victor Danilchenko wrote:
Hi,
I am trying to set up a database server with multiple DB
clusters, so that in each cluster a number of users have their own
database each, with passwordless access (we can trust the network
security in our installation). The following is what seems like
Tom Lane wrote:
> Scott Marlowe <[EMAIL PROTECTED]> writes:
> > On Mon, 2005-01-24 at 12:05, Tom Lane wrote:
> >> In the context of online backup operations, that advice isn't relevant
> >> anymore ...
>
> > Really, is this an 8.0 thing then, that I can make file system backups
> > and expect them
Donald Fraser wrote:
I have a standard Redhat 9 installation with the exception of
upgrading bison to bison-1.875-7.1
I can build the postgres rpm files from the source for version 7.4.5
no problems with the following command: rpmbuild --rebuild --define
'build89 1' --define 'python 0' --define 'te
12 matches
Mail list logo
