g for openssl/ssl.h... no
configure: error: header file is required for OpenSSL
Any ideas?
- --
Jonathan Gardner
[EMAIL PROTECTED]
Live Free, Use Linux!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/w4lOWgwF3QvpWNwRAmMCAKC+e17ogRA/uNHdMT3FbMOq3fivawC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 25 November 2003 9:13 am, Joe Conway wrote:
> ./configure --with-openssl --with-krb5=/usr/kerberos
That seems to do the trick. Thanks for the help!
- --
Jonathan Gardner
[EMAIL PROTECTED]
Live Free, Use Linux!
-BEGIN PGP SIGNAT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 25 November 2003 9:15 am, Tom Lane wrote:
> Jonathan Gardner <[EMAIL PROTECTED]> writes:
> > I have a bit of a problem getting PostgreSQL 7.4's configure script to
> > recognize openSSL.
>
> Weird. Maybe s
Leaving directory
`/home/jgardner/src/postgresql-7.4/src/backend/bootstrap'
make[2]: *** [bootstrap-recursive] Error 2
make[2]: Leaving directory `/home/jgardner/src/postgresql-7.4/src/backend'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/jgardner/src/postgresql-7.4/src'
new one.
It'll look like this:
$ pg_dumpall (old database options) | psql (new database options) template1
--
Jonathan Gardner
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
QL are you trying to install?
- --
Jonathan Gardner <[EMAIL PROTECTED]>
(was [EMAIL PROTECTED])
Live Free, Use Linux!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+4Qm4WgwF3QvpWNwRAsxCAKCRpJTX7vn5K26POw9dnkJwIwvjEACgizDA
r3a70EywQY6EtpQHOxL
d track how indexes and variations on statements will affect
performance.
I think this is fundamental to any performance tweaks. If you have no way to
control the traffic to the server, and you have no way of measuring the
performance, how can you tell if what you did helped or hurt?
- -
kup file and it keeps asking me for a new password each time. Is there
> an easier way than examining the file and carefully following the connect
> statement orders and entering the correct password. (btw there are over 100
> connect statements).
>
Try ~/.pgpass with one line:
*:*:
>
> I think that output will go to stderr.
>
- From Bash, you can use the common idiom "2>&1".
# the_command 2>&1 >> the_logfile
This will capture stderr as well as stdout.
- --
Jonathan Gardner <[EMAIL PROTECTED]>
(was [EMAIL PROTECTED])
Live Fr
tory of the user.
It should have a line:
*:*:*::
- --
Jonathan Gardner <[EMAIL PROTECTED]>
(was [EMAIL PROTECTED])
Live Free, Use Linux!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+36W3WgwF3QvpWNwRAnvkAJ4zcFGBMemqGRqYTRTdcPQTZqUvwACeMmIn
Lgiq5VrDOowcpmdSbn5E
umps a bunch of SQL
commands.
This is also a cheap way to "vacuum" the database:
# pg_dump | gzip > dump.gz
# dropdb
# createdb
# gunzip -c dump.gz > psql
- --
Jonathan Gardner <[EMAIL PROTECTED]>
(was [EMAIL PROTECTED])
Live Free, Use Linux!
-BEGIN PGP SIGNAT
to subscribe. You were the one who sent the confirmation. You are the
one who should take the time to learn how to do it yourself.
- --
Jonathan Gardner <[EMAIL PROTECTED]>
(was [EMAIL PROTECTED])
Live Free, Use Linux!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.
can be used for this ?
>
Why in the world would you want to? Think about this for a moment: The script
runs in under a second - why would it want to sit around and wait for a
notification?
- --
Jonathan Gardner <[EMAIL PROTECTED]>
(was [EMAIL PROTECTED])
Live Free, Use Linux!
---
nt to record transaction history on a table, you'll need to use
triggers and a separate table to store the history in. When the transaction
that modified the table commits, the modification to the history table from
the trigger will commit also, in the order they committed.
- --
Jonatha
you have no options but to
abandon Access.
- --
Jonathan Gardner <[EMAIL PROTECTED]>
(was [EMAIL PROTECTED])
Live Free, Use Linux!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+8cSgWgwF3QvpWNwRApg3AJ9VCLFOWmuxrfVS2DL8f8e1M2enWQCfSO+c
DoT/2UWQY1vJ1W2WP2Cm
go for a server-side solution (because the application doesn't know
what was last inserted and when), then you'll want to use triggers as I
described in a previous posting.
- --
Jonathan Gardner <[EMAIL PROTECTED]>
(was [EMAIL PROTECTED])
Live Free, Use Linux!
-BEGIN PGP
will pass back all the
data you need. You get a free transaction block inside the stored procedure
as well.
- --
Jonathan Gardner <[EMAIL PROTECTED]>
(was [EMAIL PROTECTED])
Live Free, Use Linux!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8
of the servers goes down, the whole thing will still work. You can also
add databases to the system on-the-fly. That way, you can always keep one (or
two or three) extra stand-by databases.
- --
Jonathan Gardner <[EMAIL PROTECTED]>
(was [EMAIL PROTECTED])
Live Free, Use Linux!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 30 June 2003 09:17, [EMAIL PROTECTED] wrote:
> On Mon, Jun 30, 2003 at 08:31:09AM -0700, Jonathan Gardner wrote:
>
> * currently only an explicit sync-out is supported - from time to time
> evry table has to be scanned for new
database names.
>
> Connect to PostgreSQL with psql
>
> psql template1 -U postgres
>
> Then enter \l command:
>
$ psql -l
will do the trick as well.
- --
Jonathan Gardner <[EMAIL PROTECTED]>
(was [EMAIL PROTECTED])
Live Free, Use Linux!
-BEGIN PGP SIGNATURE-
20 matches
Mail list logo
