Is it advisable or ok to install v8.2.5 to a Red Hat 9 configuration? I
tried it and there are a lot of libraries that I need get and install (e.g.
libc). I am wondering if it is worth it (or dangerous) or am I better off
upgrading my system?
Thanks
Tony
Onward Upward!
* Andrew Sullivan:
(For instance, a DNS company runs completely different name server code on
completely different hardware and OS platforms in order to make sure not to
be vulnerable to day-0 exploits. That kind of thing.)
This only helps against crasher bugs. For code injection, it's
On Fri, 28 Dec 2007, Anthony B. Colson wrote:
Is it advisable or ok to install v8.2.5 to a Red Hat 9
configuration?
No.
It is not ok to run any RedHat Linux, as thay are totally not
supported and insecure.
You should as soon as possible install RedHat Enterprise 5 (or a
clone like CentOS 5).
People tend to like the idea of PL/R, because R draws some awfully
nice (and frequently useful) eye candy, and it sounds cool to be able
to make such things from inside PostgreSQL. In my (probably very
limted) experience those people often find that it's harder than it
looks to make these plots
Is it advisable or ok to install v8.2.5 to a Red Hat 9 configuration? I
tried it and there are a lot of libraries that I need get and install
(e.g.
libc). I am wondering if it is worth it (or dangerous) or am I better off
upgrading my system?
Thanks
Tony
Onward Upward!
Hi Josh,
This is exactly the same setup I'm currently testing. For those
asking why use both WAL shipping and slony, it's simple; this means
we have no single point of failure. If slony stops replicating
because we mess up a replication set or our shipping method (NFS)
falls on its ass, at least
On Fri, Dec 28, 2007 at 11:21:53AM +0100, Florian Weimer wrote:
This only helps against crasher bugs. For code injection, it's
devastating if the attacker can compromise one node, and by
diversifying, he or she can choose which code base to attack.
Well, it also helps in your robustness
Folks
i received the follow message from backend ,it's this
a bug?
best regards
and happy new year
MDC
pd: any clue are welcomed.
*** glibc detected *** postgres: postgres richelet
201.235.11.133(2504) SELECT: double free or corruption
(!prev): 0x0845d7e8 ***
=== Backtrace:
On Dec 28, 2007, at 9:33 AM, marcelo Cortez wrote:
Folks
i received the follow message from backend ,it's this
a bug?
best regards
and happy new year
MDC
pd: any clue are welcomed.
*** glibc detected *** postgres: postgres richelet
201.235.11.133(2504) SELECT: double free or
marcelo Cortez [EMAIL PROTECTED] writes:
*** glibc detected *** postgres: postgres richelet
201.235.11.133(2504) SELECT: double free or corruption
(!prev): 0x0845d7e8 ***
What PG version is this? Can you provide a reproducible test case?
regards, tom lane
Folks
sorry i forgot to mention
i'm developing one c external program, may be fault is
my code , but surprise to me the message, what bad
practice generate this behavior?
fail seems to be not to reproducible all times,
i'm using beta3 version, it's this important?
select version:
PostgreSQL
Hi
I created a database instance and a database takign whatever defaults
were in effect with regard to defining a superuser and password. What
are those defaults? How do I change the password for the superuser?
Thanks
-dave
marcelo Cortez [EMAIL PROTECTED] writes:
sorry i forgot to mention
i'm developing one c external program, may be fault is
my code , but surprise to me the message, what bad
practice generate this behavior?
fail seems to be not to reproducible all times,
i'm using beta3 version, it's this
Hi,
Thanks for all your response.
I also thought abt having 2 setups for backup and replication so that even
when slony fails I will always have the standby server (WAL shipping) to
help me out.
I have another question regarding this. I also want to write these to the
tape. Right now we have a
Erik Jones [EMAIL PROTECTED] writes:
Well, if Postgres had killed the proc itself it would have written
out a nicely formatted Postgres-style memory context report along
with an ERROR message along the lines of OUT OF MEMORY and the
request size and Postgres would not have bounced.
Hi,
I have postgresql version 8.3beta3 running. I want to apply a patch (
gzn7ImULlK3v.gz patch for index-only scan) to this and try it out. How to
apply this patch. Where should the patch be placed and what command to be
run. Should I have to stop the postgres server or run initdb for the patch
Gauthier, Dave wrote:
Hi
I created a database instance and a database takign whatever defaults
were in effect with regard to defining a superuser and password. What
are those defaults? How do I change the password for the superuser?
You created a database or a cluster? What command did
I think I created a cluster (initdb) and then a database (createdb
mypgdb).
I believe I am the default superuser (my linux uid). At least I appear
to own everything using psql -l. And I needn't identify myself when
making a db connection through that user.
I then created a user that I wanted to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 28 Dec 2007 12:59:28 -0500
Gauthier, Dave [EMAIL PROTECTED] wrote:
And I can connect using the foo user (psql -U foo mypgdb). But it
doesn't seem to require the password. Would you know why? I would
like to use the password protection.
On Thursday 27 December 2007 12:23, Samantha Atkins wrote:
On Dec 24, 2007, at 11:15 PM, Greg Smith wrote:
This may be better because it isn't doing the query first. You may
discover that you need to aggressively run one of the VACUUM
processes (I'd guess regular and ANALYZE but not FULL)
On 12/28/07, Robert Treat [EMAIL PROTECTED] wrote:
On Thursday 27 December 2007 12:23, Samantha Atkins wrote:
Since it is known to be dead
is it automatically removed when there are no live transaction that
reference or may reference it and its data page space marked available
for new
On Fri, 28 Dec 2007, Robert Treat wrote:
A given transaction doesn't have a way to determine if there are live
transaction looking at the row, that would require quite a bit of
knowledge about what else is occuring in the system to be able to
determine that. That level of knowledge/complexity
22 matches
Mail list logo
