happening is that it's compiling the test program to
link dynamically to libreadline (which is fairly normal), but then LD
can't actually find libreadline anywhere. Try man/google for ld.conf.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some
x27;s)?
Or may be more convenient way to rewrite SELECT WHERE clause on per-
session bases exist (similar to RULES)?
Thanks.
Search pgFoundry for veil; I believe it will do what you want.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Description: S/MIME cryptographic signature
I would not
expect you to have any major code issues going to 8.0 or 8.1. Of
course going to 8.3 would be better, but you could run into some
compatibility issues. You'll get a performance gain to boot.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your compu
systems, I've had trouble removing database files because upgrades
use certain files from old versions. I don't want to break my new
database. I'm on Solaris 10.
Not only does the new version not use files from the old, it doesn't
even know it exists. You can just nuke
base, to refresh the view, drop the
table, but everything gives me that message.
Does anyone have any idea what could I do to solve this problem?
The postgres version is: 7.4_7.4.16
What's it do in psql?
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer so
LACE FUNCTION Z
RETURNS "trigger" AS
$BODY$
begin
if (tg_op in ('INSERT', 'UPDATE', 'DELETE')) then
update A;
end if;
$BODY$
LANGUAGE 'plpgsql' VOLATILE;
Can't help much with your fake example, but I am wondering why you
h
index, especially in 7.4.
And yes, upgrade. At a minimum you need to get to the lastest 7.4,
which doesn't require anything special.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Description: S/MIME cryptographic signature
On Tue, Feb 05, 2008 at 10:11:31PM -0500, Tom Lane wrote:
> Decibel! <[EMAIL PROTECTED]> writes:
> > On Tue, Feb 05, 2008 at 05:57:31PM -0500, Tom Lane wrote:
> >> We have no user-facing documentation on TOAST, either, which would seem
> >> to me to be at least as
t; We have no user-facing documentation on TOAST, either, which would seem
> to me to be at least as much of a candidate for people to custom-design
> their databases around. In practice I don't think anyone does.
Uh... http://www.postgresql.org/docs/8.3/interactive/storage-toast.htm
On Oct 7, 2007, at 11:37 AM, Faber Fedor wrote:
Is SLONY/replication my only choice? Remember, I can't/don't want to
rebuild the existing servers.
Slony is. As an added benefit, it will allow you to perform a
migration with effectively zero downtime.
--
Decibel!, aka Jim C. Nasby
e of documenting the details of how
(archive|recovery)_command is used; one of the huge benefits of our
system over others is the flexibility you have in being able to run
whatever command you want.
I know Simon was working on some improvements to the PITR docs, but I
don't know if that'
ything).
You might also be able to UPDATE the appropriate catalog, but I'm not
sure how safe that is.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpjuYEmOrakm.pgp
Description: PGP signature
OS side or on Postgres side) for starting postgres?
#define "postgres window"
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpqY8Cs3pxlq.pgp
Description: PGP signature
on for that user instead.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpTWu00WwUAH.pgp
Description: PGP signature
er, then the command is blocking waiting for postmaster to
> exit.
So let it stop, start the timer, then start it again.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpgqC02qX484.pgp
Description: PGP signature
ff at random times without vacuum cost delay. Vacuuming
key tables more frequently via cron might be a better strategy, but if
you do want to run pg_autovac I've got a script that will help.
BTW, http://decibel.org/~decibel/pervasive/fsm.html is something I wrote
while at Pervasive that exp
nd restore,
you should really use that opportunity to upgrade to a modern version,
too.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpoD7ZtXPhkX.pgp
Description: PGP signature
D for one) will respect process priority when it comes to
scheduling IO as well, so if you nice the backup process it hopefully
wouldn't impact the database as much.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpIlIXrpCntA.pgp
Description: PGP signature
led with a signal 11. IIRC, that
indicates faulty hardware.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpDTNPqoiujL.pgp
Description: PGP signature
or inability to
connect to the central location would mean no backup.
As for performance, just how hard are you pushing these machines?
Copying a 16MB file that's already in memory isn't exactly an intensive
operation...
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpgJNm0Oojd0.pgp
Description: PGP signature
are identical then you shouldn't have
lost any data... if they are then you probably have.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgprSE9IswoO9.pgp
Description: PGP signature
together so that
> 'pg_restore' would not find it incorrect. I had to make a 'ls | cat | psql
> databasename'. After 15 hours of work nothing changed! :)
Why not? Plain text should still work fine. I've seen it done on 300G
databases.
--
Decibel!, aka Jim Nas
iles anymore. Another possibility would be to
ensure that things are configured so that each machine will archive to a
different location.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgp5osyYXdpDL.pgp
Description: PGP signature
the docs above?
No... if you want incremental backups, use PITR. Someone's done some
work on an incremental version of pg_dump, but I haven't heard anything
about it in about a year.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpY8wJ8swJIk.pgp
Description: PGP signature
-commit,
that will give you an idea of what gets backported (though often
threads are just discussions; you may have to hunt to find some
backpatching ones).
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell
he_size to the same. If you'll be growing
larger than 500MB or so, I'd set effective_cache_size to 875000. If
you move up to a current release, you could set shared_buffers much
higher, but I wouldn't go much past 1GB (131072) in 7.4.
remove NSPAM to email
If you want folks
26 matches
Mail list logo
