Werner Bohl wrote:
Hi!
Hope anybody can help me with this issue. I have a fairly large table
(~75 million rows) that where imported without pk. Tried to create a pk
on a supposed unique field, but failed with duplicates. So i issued:
select oldid from table group by oldid having count(*) > 1
and it
> From: Tom Lane
> "Simon Riggs" <[EMAIL PROTECTED]> writes:
> > On top of a confusing day, I now have this:
> > I set log_duration = true in a postgresql.conf file.
> > I startup and test, local users connected via psql:
> working, no problem.
> > Users connecting remotely, same user, same databas
Michael Klatt <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> [ thinks about that... ] Hmm, you're right, there is no mechanism to
>> cause the flat password file to be rebuilt after a restore.
> Do you think a fix will show up in 8.0.2?
Not sure; a proper fix may have to wait for 8.1. The ide
Tom Lane wrote:
[ thinks about that... ] Hmm, you're right, there is no mechanism to
cause the flat password file to be rebuilt after a restore. So newly
created users won't be in it (and for that matter it won't reflect
post-backup password changes for existing users). Just (re)assign any
one u
I have just built PostgreSQL 8.0.1 in my Solaris 10 x86 box (32-bit)
just now. You would need to install the libraries needed either through
http://www.blastwave.org or http://www.sunfreeware.com, i recommend the
former.
regards,
-
Jonel Rienton
http://blogs.road14.com
Software Developer, *
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> On top of a confusing day, I now have this:
> I set log_duration = true in a postgresql.conf file.
> I startup and test, local users connected via psql: working, no problem.
> Users connecting remotely, same user, same database: no log of query
> statemen
On top of a confusing day, I now have this:
I set log_duration = true in a postgresql.conf file.
I startup and test, local users connected via psql: working, no problem.
Users connecting remotely, same user, same database: no log of query
statement durations.
There is nothing in the code that s
Hi!
Hope anybody can help me with this issue. I have a fairly large table
(~75 million rows) that where imported without pk. Tried to create a pk
on a supposed unique field, but failed with duplicates. So i issued:
select oldid from table group by oldid having count(*) > 1
and it fails with Out of
On Feb 4, 2005, at 12:08 PM, Tom Lane wrote:
No, no, and no. A 7.2.anything server would flat out refuse to start
in
a 7.3.* database (because it checks PG_VERSION). You might have been
using 7.3 client-side code to talk to the 7.2 server, but that wouldn't
cause this sort of failure.
A possibl
Gary Jackson <[EMAIL PROTECTED]> writes:
> We have a problem with a PosgreSQL database where the user cannot get
> to their tables any more. I am not the primary administrator of this
> host (who is on vacation), nor am I the user of this database. The
> /var/log/posgresql file has entries lik
Michael Klatt <[EMAIL PROTECTED]> writes:
> I love the online backup feature, but I'm encountering a problem with
> users restored from WAL files. It seems that after a restore, the
> password for any user created since the base backup is broken.
[ thinks about that... ] Hmm, you're right, the
We have a problem with a PosgreSQL database where the user cannot get
to their tables any more. I am not the primary administrator of this
host (who is on vacation), nor am I the user of this database. The
/var/log/posgresql file has entries like the following, at the end:
FATAL 1: Database
"Rod MacNeil" <[EMAIL PROTECTED]> writes:
> I have a need to install multiple versions on my linux box (7.1.2 & 7.4.x on
> FC3). Both will be installed from source. I know that they will need separate
> install and data directories and use sepearate ports. My question is about
> the libraries. I
PostgreSQL 8.0.1
Linux FC2, 2.6.8
Hi,
I'm very new to PostgreSQL. I've been the admin of several MySQL
servers for years, but for various reasons we're switching to PostgreSQL.
I love the online backup feature, but I'm encountering a problem with
users restored from WAL files. It seems that af
Title: help
On Thu, Feb 03, 2005 at 04:03:40 -0500,
Zeki Mokhtarzada <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I recently tried to upgrade from postgresql8.0beta4 to 8.0.1. When I
> tried to start postmaster I got the following error:
>
> FATAL: database files are incompatible with server
> DETAIL: T
Simon Riggs writes:
> >Mark Reidenbach wrote
>
> >The problem I'm having is that you need to
> > backup this wal
> > file before it's been archived to have a backup which is
> > consistent
>
> Not sure I agree. Can you explain some more?
>
> Is it that you have a very low transaction rate and lo
On Thu, Feb 03, 2005 at 05:42:31PM +0530, Sanjay Rathod wrote:
> Can you please let me know whether the Postgres 8.0 version available for
> Solaris-sparc
You can build PostgreSQL 8.0.1 from source on Solaris 9 sparc.
I use gcc 3.4.2 on that platform and PostgreSQL compiles and
passes all regres
18 matches
Mail list logo
