On Wed, Apr 9, 2008 at 4:47 PM, Mikko Partio <[EMAIL PROTECTED]> wrote:
> Hello all
>
> my struggle with the database continues (see earlier thread titled "too
> many trigger records found for relation xyz").
>
> Today, I created yet another to table to the same database. Everything
> went ok, no
On Montag, 14. April 2008 Tom Lane wrote:
> What PG version is this?
I've looked a little more into history, and PostgreSQL was 8.1.5
originally from CD, then 8.1.9 and now 8.1.11.
I'm currently investigating a way to delete duplicates from the table.
Is there any chance to do that? A
SELECT *
hi alli have a backup of data folder of my old postgresql
database on 7.54now i want to restore my complete database
from data folder in ver 8.1so can any gurus give me the idea
about itYogeshSenior Officer (System)
--
This message has been scanned for viruses and
dangerous content by
BanasDairy
I am developing a wxPython app which can run, like Postgresql, on Linux and
Windows boxes.
Linux users are far more specialized than Windows one - and Postgres comes
along with major distros.
Windows users don't want (or are unable to) install Postgresql by
themselves, so I was wondering if there
Thanks for the info on TOAST. We're still finding our legs with Postgres after
several years on MySQL.
We do have the flexibility to adjust our data types and schema if we need to.
We try to keep it to a minimum, but it's doable. I'm completely open to the
possibility that we just have a ve
"Phillip Smith" <[EMAIL PROTECTED]> writes:
>> Here's my interpretation of those results: the TOAST tables for
>> our image files are compressed by Postgres. During the backup,
>> pg_dump uncompresses them, and if compression is turned on,
>> recompresses the backup. Please correct me if I'm wron
Hi,
I have never dealt with tables that are made
of compressed data, but I back up the database
via crontab file like this:
.
.
filename=`date +%G%m%d.%w`.gz
/usr/local/pgsql/bin/pg_dumpall | gzip > /some_destination/$filename
.
.
(Sorry, hit send too soon!)
> I ran pg_dump with the arguments you suggested, and my 4 GB test
> table finished backing up in about 25 minutes, which seems great.
> The only problem is that the resulting backup file was over 9 GB.
> Using -Z2 resulting in a 55 minute 6GB backup.
>
> Here's my int
> I ran pg_dump with the arguments you suggested, and my 4 GB test table
finished
> backing up in about 25 minutes, which seems great. The only problem is
that the
> resulting backup file was over 9 GB. Using -Z2 resulting in a 55 minute
6GB backup.
>
> Here's my interpretation of those results:
The images are stored in whatever format our users load them as, so we
don't have any control over their compression or lack thereof.
I ran pg_dump with the arguments you suggested, and my 4 GB test table
finished backing up in about 25 minutes, which seems great. The only
problem is that the re
Hi Everybody,
I found a solution by trial and guessing.
I explicitly coded:
LD_LIBRARY_PATH=/usr/local/pgsql/lib
in the crontab file. That seems to have
done it.
Regards,
Tena Sakai
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] on behalf of Tena Sakai
Sent: Mon 4/14/2
Hi Tena,
Thanks very much for your info.
I have installed PostgreSQL 8.3 on 5431 port, and on the same machine 8.1 is
running on 5432 port.
i have taken the backup file from 8.1 and restored into 8.3 using pgadminIII
tool. I got he db into 8.3. As i am using hibernate everything looks fine.
How e
Hi,
I consider myself poor, inexperienced postgres
administrator (which is not really my job, but
we cannot afford a dba), but I moved from 8.2.3
to 8.3.0 about a month ago. It took some planning
and reading, but with the preparation I did, it
went pretty smooth. Just my 2 bits as a first-
hand
On Montag, 14. April 2008 Alvaro Herrera wrote:
> What do you mean "shared from 2 servers"? Are these two servers
> using a shared network mount with the database files? Or do you mean
> that these two servers connect as clients to a single Postgres
> server?
Two servers have SA running, and con
Hi Everybody,
My postgres version:
PostgreSQL 8.3.0 on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 3.4.6
20060404 (Red Hat 3.4.6-3)
I can reindex a table from psql. At psql prompt,
I type: reindex table foo;
and it returns
REINDEX
followed by another prompt.
I am trying to get the same
On Montag, 14. April 2008 Tom Lane wrote:
> What PG version is this?
Sorry:
# select version();
version
PostgreSQL 8.1.11 on i686-pc-linu
Michael Monnerie wrote:
> Dear list, I don't know whether pgsql-admin or the SA list is the
> correct one to ask, so I start here. I have a bayes Postgres database
> for SpamAssassin, which I use shared from 2 servers to have the same
> content. I think this could be a locking issue or whatever,
Michael Monnerie <[EMAIL PROTECTED]> writes:
> care. BUT: I have lots of "duplicate index" elements now, preventing a
> restore or cleanup.
What PG version is this?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to yo
Dear list, I don't know whether pgsql-admin or the SA list is the
correct one to ask, so I start here. I have a bayes Postgres database
for SpamAssassin, which I use shared from 2 servers to have the same
content. I think this could be a locking issue or whatever, I don't
care. BUT: I have lots
Darren Reed <[EMAIL PROTECTED]> writes:
> See if the attached helps.
Well, here's the entry for the index it's trying to load:
> Item 12 -- Length: 164 Offset: 6224 (0x1850) Flags: USED
> XMIN: 1 CMIN: 0 XMAX: 667033 CMAX|XVAC: 6 OID: 2701
> Block Id: 7 linp Index: 3 Attributes: 2
Darren Reed <[EMAIL PROTECTED]> writes:
> Some time ago I saw this message:
> ERROR: index "pg_depend_reference_index" contains unexpected zero page
> at block 23
> HINT: Please REINDEX it.
> ERROR: index "table_p_hash_idx" contains unexpected zero page at block 7
> HINT: Please REINDEX it.
[
Tom Lane wrote:
Darren Reed <[EMAIL PROTECTED]> writes:
> Program terminated with signal 11, Segmentation fault.
> #0 0x0829845c in RelationCacheInitializePhase2 () at relcache.c:2400
> 2400LOAD_CRIT_INDEX(TriggerRelidNameIndexId);
> (gdb) where
> #0 0x0829845c in RelationCa
Darren Reed <[EMAIL PROTECTED]> writes:
> Program terminated with signal 11, Segmentation fault.
> #0 0x0829845c in RelationCacheInitializePhase2 () at relcache.c:2400
> 2400LOAD_CRIT_INDEX(TriggerRelidNameIndexId);
> (gdb) where
> #0 0x0829845c in RelationCacheInitializePhase
Thanks for all your advices, it worked perfectly.
I only had to build again postgres with the option : ./configure
--enable-integer-datetimes
due to the error:
"DETAIL: The database cluster was initialized
without HAVE_INT64_TIMESTAMP but the server was compiled with
HAVE_INT64_TIMESTAMP.
I did
24 matches
Mail list logo
