Wow, nice analysis. Should this be in our documentation somewhere?
---
Christopher Browne wrote:
> In the last exciting episode, [EMAIL PROTECTED] (Joseph Brenner) wrote:
> > I was talking to someone just recently who was s
In the last exciting episode, [EMAIL PROTECTED] (Joseph Brenner) wrote:
> I was talking to someone just recently who was saying that they
> were thinking about going with Oracle rather than Postgresql
> because Oracle has a their story in place about how to do
> disk encryption. So I am of course
On Fri, Apr 01, 2005 at 12:37:51PM +0530, sharma;G.S. wrote:
>
> I want to rename and modify the data type of a column in postgres 7.3
> can any body help me ...that it is possible to do the above in postgres
> and if yes pls provide me the syntax
You can rename columns with ALTER TABLE:
http://w
Thanks, for the input.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
Sent: Friday, April 01, 2005 1:49 PM
To: [EMAIL PROTECTED]
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Help understanding VACUUM info on 7.4.5
"Chris White \(cjwhite
Joseph Brenner <[EMAIL PROTECTED]> writes:
> I was talking to someone just recently who was saying that they
> were thinking about going with Oracle rather than Postgresql
> because Oracle has a their story in place about how to do
> disk encryption. So I am of course, looking into how to do it
>
Humm, I am unaware of any Oracle feature that does disk encryption.
There is a built-in package that allows one to encrypt the data as it is
on it's way to the table, but nothing to encrypt the data on it's way to
the disk. Your friend may have been mislead by the fact that Oracle
writes it's data
On Fri, Apr 01, 2005 at 13:43:01 -0800,
Joseph Brenner <[EMAIL PROTECTED]> wrote:
>
> (As to why you would *care* about disk encryption, I would guess
> the scenario is you've got a bunch of guys in the back room
> hot-swapping RAID drives, and you'd rather not post armed guards
> there to watch
"Chris White \(cjwhite\)" <[EMAIL PROTECTED]> writes:
> Does this mean it could be any transaction, even one that has not done
> anything with large objects, but one that started prior to the large objects
> being deleted?
Exactly.
> All access to the DB is done via JDBC, so has this JDBC issue b
I was talking to someone just recently who was saying that they
were thinking about going with Oracle rather than Postgresql
because Oracle has a their story in place about how to do
disk encryption. So I am of course, looking into how to do it
with Postgresql...
(As to why you would *care* ab
Does this mean it could be any transaction, even one that has not done
anything with large objects, but one that started prior to the large objects
being deleted?
All access to the DB is done via JDBC, so has this JDBC issue been fixed in
7.4.5?
Chris
-Original Message-
From: [EMAIL PROT
"Chris White (cjwhite)" <[EMAIL PROTECTED]> writes:
> Below I have info which shows a DB which has had all objects deleted and
> then vacuumed. As can been seen it say it has "9014 dead rows that can't
> been removed". What does that mean?
That means there's an open transaction that is old enough
Please do not respond last email, only this...
public int cedula_actualizar(String strcedula, String strids) {
PreparedStatement ST = null;
int retVal = 0;
try {
ST = conexion.prepareStatement("UPDATE maestro_partes SET
cedula=? WHERE consecutivo_identificacion I
public int cedula_actualizar(String strcedula, String strids) {
PreparedStatement ST = null;
int retVal = 0;
try {
ST = conexion.prepareStatement("UPDATE maestro_partes SET
cedula='"+strcedula+"' WHERE consecutivo_identificacion IN ("+strids+")");
retV
Hi,
I am running
Postgres 7.4.5 and am storing binary objects in the largeobject table. We want
to keep the size of the database and especially the large object table to a
minimum, so we vacuum it (not full) on a regular basis. However, what we have
seen is that even after deleting entries
On Fri, 1 Apr 2005, Tom Lane wrote:
> "L.Boldareva" <[EMAIL PROTECTED]> writes:
> > Here is how I got it crashed:
> > I compiled a c-procedure and copied the .so file to its place exactly at a
> > time when (quite unfortunately) another query was running, that used that
> > library.
>
> Hmm, at w
"L.Boldareva" <[EMAIL PROTECTED]> writes:
> Here is how I got it crashed:
> I compiled a c-procedure and copied the .so file to its place exactly at a
> time when (quite unfortunately) another query was running, that used that
> library.
Hmm, at worst that should only crash one backend, not result
I have kind of fixed the problem (hopefully)
I turned out I used plan B, dump/reload will be my next step then.
What is meant by the "corrupt data", is this about the data or the things
around it, like indexes, system tables?
Here is how I got it crashed:
I compiled a c-procedure and copied the .
On Fri, 2005-04-01 at 04:02, L.Boldareva wrote:
> Hi!
> (Hope this is the right place to post)
>
> I crashed the postmaster and cannot start it anymore, with the error
In addition to what everyone's posted already, I would suggest you spend
some time figuring out what got you here in the first pl
Ok, looks like I kind of fixed it.
(after tarring data/) I ran pg_resetxlog -f , although it's not meant to
fix this problem.
The database starts up now, but the last created couple of tables are
coppupted, so that it cannot be reindexed or vaccumed, and
there is an error in a system table:
Pos
"L.Boldareva" <[EMAIL PROTECTED]> writes:
> LOG: database system was not properly shut down; automatic recovery in
> progress
> LOG: redo starts at 5/6F000ABC
> PANIC: btree_split_redo: lost left sibling
> LOG: startup process (PID 5603) was terminated by signal 6
Hmm. AFAICS that could only
Hi,
We are migrating to a new server with more memory and also from
postgres 7.4 to postgres 8.0.1 version.
Here are my settings on the current 7.4 version:
OS : RedHat 9
CPUS: 2 hyperthreaded
Memory: 4gig
shared_buffers: 65536
sort_mem: 16384
vacuum_mem: 32768
wal_buffers: 64
effective_cache_s
Simon Riggs wrote:
On Thu, 2005-03-31 at 18:41 -0500, Jason DiCioccio wrote:
Now, realize that ..0022 was not in the archive directory, and
actually is still not. However, it seems to be requiring it. Do I
have to wait for this log to be archived?
Yes.
Is there a way that I can
forc
"L.Boldareva" <[EMAIL PROTECTED]> wrote on 01.04.2005, 12:02:21:
> Hi!
> (Hope this is the right place to post)
>
> I crashed the postmaster and cannot start it anymore, with the error
>
> LOG: database system was interrupted while in recovery at 2005-04-01
> 11:04:33 CEST
> HINT: This proba
Hi!
(Hope this is the right place to post)
I crashed the postmaster and cannot start it anymore, with the error
LOG: database system was interrupted while in recovery at 2005-04-01 11:04:33
CEST
HINT: This probably means that some data is corrupted and you will have to use
the last backup fo
24 matches
Mail list logo
