Lucio wrote:
This application uses a static (read-only, no insert, modify or delete) 200MB
postgresql db, so can't put pgsql/data/base and pgsql/data/pg_xlog in ramdisk.
One thing I don't think I saw mentioned yetI think certain queries
create temporary tables (or at least use some temporary
Lucio wrote:
Hi,
I'am trying to create a demo cd (knoppix) with a jdbc application.
This application uses a static (read-only, no insert, modify or delete) 200MB
postgresql db, so can't put pgsql/data/base and pgsql/data/pg_xlog in ramdisk.
One thing I don't think I saw mentioned yet
I think
On Wed, Nov 19, 2003 at 05:17:27PM +, Gary Stainburn wrote:
Is it possible to recover a database from a dump + some form of
transaction log, i.e. if I pg_dump on a nightly basis, and then at
noon the database crashes, can I take the last dump and roll it
forward from a log.
No.
(Is
Hello dba's
Im playing around with the BR features of PostgreSQL 7.4 for a
PostgreSQL-BR course.
Q1: Let's imagine, we have a database cluster containing DB1, DB2 and
DB3. System (disk) crashes and we are only able to recover DB2 (was on a
local disk not on the external like DB1 and DB3).
Sander Steffann [EMAIL PROTECTED] writes:
I think there is some confusion about which PostgreSQL is included in RHEL3.
I just checked and the following packages are in RHN channel Red Hat
Enterprise Linux ES (v. 3 for x86):
[snip]
Right. Note the lack of any server-side packages. Only
On Thu, 2003-11-20 at 11:09, Oli Sennhauser wrote:
Hello dba's
Im playing around with the BR features of PostgreSQL 7.4 for a
PostgreSQL-BR course.
Q1: Let's imagine, we have a database cluster containing DB1, DB2 and
DB3. System (disk) crashes and we are only able to recover DB2 (was
Hi,
Sander Steffann [EMAIL PROTECTED] writes:
I think there is some confusion about which PostgreSQL is included in
RHEL3.
I just checked and the following packages are in RHN channel Red Hat
Enterprise Linux ES (v. 3 for x86):
[snip]
Right. Note the lack of any server-side packages.
Title: Message
Hi ,
I'm facing an issue with
Postgresql 7.3.4.
I've installed
DBIversion 1.37 DBD::Pg (1.22) on a Solaris8 machine w/ perl 5.6.1
.The basicproblem is I can connect to Postgres just fine from the command
line, but itcraps out when I try from a CGI with the below error
In the past, I have always put the LD_LIBRARY_PATH environment setting in the
/etc/profile (make sure to export it if necessary) and that seemed to solve all
my problems.
Make sure you are setting the LD_LIBRARY_PATH _environment_ variable in your cgi
not just a varible named LD_LIBRARY_PATH.
Hi Matt,
Thanx for the response. Actually I did put the
LD_LIBRARY_PATH as $ENV{LD_LIBRARY_PATH}=
Hope you meant the same way. Somehow it doesn't workout.
Secondly since I done have access to /usr/local or /etc/profile
I did install the postgresql and DBD::Pg as per below.
I've had this problem (or something very similar) happen before several
times on new installations. I think I resolved it by re-installing
DBD::Pg - but this was a while ago.
Are you sure Pg.so is in your @INC path?
Try adding this to your CGI to be sure it's looking in the right place.
use lib
I just installed PgSQL and PhpPgAdmin with apt-get on Debian. How do I
login to PhpPgAdmin, since I have no idea of the login information?
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
12 matches
Mail list logo