Am 2008-09-24 15:20:03, schrieb Carol Walter:
> Hello,
>
> Does anyone know what the format of hex characters for postgres are?
> I'm trying to create files that contain a 0x55. It looks to me like
> it should require a delimiter of some sort between the characters. I
> don't know how pos
With our backup techniques, it is a bit painful to deal with WAL files
when the number goes lower and starts re-using numbers already
archived, as when we upgrade to a new release using pg_dumpall piped
to psql. We can work around it, but it would keep our environment and
scripts simpler (and ther
Hello,
I've been reading previous posts and I think I have some tables in my
database that would better be stored with fillfactor=90 or less. We are
going to upgrade and reinstall our server soon. I thought this would be
a good time to change fillfactor. Just I don't know how. First I need to
Greetings,
As you may be aware, we experienced a problem last week with pg_clogs
that had been deleted, through human error it appears. What process
will clear or delete the pg_clogs? I've been all over the
documentation and I'm not finding a reference to this.
Thanks, in advance,
Caro
Jonny wrote:
Hi,
I have installes Postgres 8.0.15 on a embedded Linux and have only 130
MB for Postgres.
Is it possible to turn off the comlete (Wal) pg_xlog? Because this is
the biggest part.
I found an Entry how to minimize the count of stored xlogs.
Is it possible to store it to /dev/null
Chander Ganesan <[EMAIL PROTECTED]> writes:
> You should also understand that if you set checkpoint_segments to a
> small number, its still possible that PostgreSQL might use more than
> that number for a large transaction.
"Large transactions" have nothing to do with this. You are confusing
Po
Tom Lane wrote:
Chander Ganesan <[EMAIL PROTECTED]> writes:
You should also understand that if you set checkpoint_segments to a
small number, its still possible that PostgreSQL might use more than
that number for a large transaction.
"Large transactions" have nothing to do with this.
I might have to disagree here. I personally experienced a scenario
where I had 500 MB of file space defined for my WAL log files and then
attempted (not thinking it through thoroughly) to perform a COPY of a
very large (1.8 GB) dataset and kept adding WAL files until my file
system filled up and t
Carol Walter wrote:
Greetings,
As you may be aware, we experienced a problem last week with pg_clogs
that had been deleted, through human error it appears. What process
will clear or delete the pg_clogs? I've been all over the
documentation and I'm not finding a reference to this.
Postgre
Ah-h-h, that's exactly my question. What part of Postgres "takes
care of this itself." I'm asking because I had 86 pg_clog files
dated back to mid-May. I got the impression from something Tom said
that backups should prune this directory. Perhaps my "impression"
was wrong. Most databas
Carol Walter wrote:
Ah-h-h, that's exactly my question. What part of Postgres "takes care
of this itself." I'm asking because I had 86 pg_clog files dated back
to mid-May. I got the impression from something Tom said that backups
should prune this directory. Perhaps my "impression" was wron
Hello,
If you want to get the value of a autogenerated column it's better to use
"RETURNING"
insert into something returning primary key...
Best Regards,
Rafael Domiciano
Postgres DBA
2008/9/15 Scott Marlowe <[EMAIL PROTECTED]>
> On Mon, Sep 15, 2008 at 11:53 AM, c k <[EMAIL PROTECTED]>
> wrot
Hello Carol,
Maybe I'm thinking wrong, but I have a problem like yours; and I realize
that the vacuum Freeze that does that work.
I have read that somewhere in the net, that I don't remember now.
To prevent that I created a proccess that run every night, that vacuums the
database, and started the
i'm trying to enable sspi authentication with the latest postgresql
(8.3.4) on windows 2003 (standard edition, sp2, latest updates).
i configured pg_hba.conf:
host all all /32 sspi
but get this error when connecting from an xp client (via pgAdmin III):
"Error connecting to the server: FATAL:
Laszlo Nagy <[EMAIL PROTECTED]> writes:
> What will this do?
> ALTER TABLE tbl SET FILLFACTOR = 90;
> Will it restucture the table, or is it just a setting and I should
> perform a VACUUM to actually reach fillfactor=90?
It's just a setting ... and VACUUM won't do much with it either.
The best
15 matches
Mail list logo
