Hi all,
I'm trying to tweak a schema creation script that works on postgres 8.x so that it will run on postgres 7.3.
I've run into trouble attempting to change the owner of a particular database. The offending line is -
ALTER DATABASE test OWNER TO epg;As I say, this works fine on postgres
Hi,
On Mon, 2006-07-17 at 12:33 +, Richard George wrote:
> I've run into trouble attempting to change the owner of a particular
> database. The offending line is -
>
> ALTER DATABASE test OWNER TO epg;
There is no way to change ownership of a database with ALTER DATABASE in
7.3.X .
> Can
thanks for this- worked a treat!
> Subject: Re: [ADMIN] Changing a database owner on postgres 7.3> From: [EMAIL PROTECTED]> To: [EMAIL PROTECTED]> CC: pgsql-admin@postgresql.org> Date: Mon, 17 Jul 2006 16:26:00 +0300> > Hi,> > On Mon, 2006-07-17 at 12:33 +, Richard George wrote:> > I've run
Title: Restarting PostgreSQL
Im working with LINUX RH 8.x ((Red Hat Linux 8.0 3.2-7); I restart my machine but when I'm trying start or restart PosgreSQl (8.0.7)
Im getting this in the log file:
LOG: could not create IPv6 socket: Address family not supported by protocol
FATAL: database
[EMAIL PROTECTED] (Devrim GUNDUZ) writes:
> Hi,
>
> On Mon, 2006-07-17 at 12:33 +, Richard George wrote:
>> I've run into trouble attempting to change the owner of a particular
>> database. The offending line is -
>>
>> ALTER DATABASE test OWNER TO epg;
>
> There is no way to change ownership
On Sat, 2006-07-15 at 02:37, adey wrote:
> Please advise if there is a way to start a fresh Postgresql error /
> output log at regular intervals?
> We are tuning a "new toproduction" system, so I have all the SQL
> logged, but the file gets too big and cumbersome, so I'd like to start
> a new one e
Hi, I am using Pgcluster 1.3 and Postgres 8.
Can you tell me meaning of this messages from pgreplicate in verbose
mode:
1. DEBUG:replicate_loop():replicate_loop selected
2. DEBUG:replicate_loop(): PGRread_packet failed query[(null)] cmdSys[]
Thanx for your time.
--
Anton P. Linevich
"Rojas, Fernando (CIAT)" <[EMAIL PROTECTED]> writes:
> FATAL: database files are incompatible with operating system
> DETAIL: The database cluster was initialized with LC_COLLATE =
> "en_US.UTF-8", which is not recognized by setlocale().
> HINT: It looks like you need to initdb or install locale
Hi Tom,
Is this 2003 advice still relevant with postgresql 8.1.0? Our b-tree
indexes corrupt pretty often on our production server running 8.1.0 and we
are grasping for a solution. We perform online backups like this: In
addition, we archive the transactions and replay them for PITR.
/us
"Mr. Dan" <[EMAIL PROTECTED]> writes:
> Is this 2003 advice still relevant with postgresql 8.1.0? Our b-tree
> indexes corrupt pretty often on our production server running 8.1.0 and we
> are grasping for a solution.
Corrupt how --- what's the exact symptoms?
The *first* bit of advice I'd giv
Hi Tom,
We do a complete re-index(reindexcb) to the cluster on the weekend.
The index corruption is characterized by incorrect result sets returned from
a query. What happens is that we have a 'hot' table (one with many many
transactions) that gets inserted and deleted often. About once a mont
"Mr. Dan" <[EMAIL PROTECTED]> writes:
> ... What happens is that we have a 'hot' table (one with many many
> transactions) that gets inserted and deleted often. About once a month now
> when we do a select from that table the results of the select do not match
> the where clause, ex.
> select *
We recently backed up our production database (dumpall) on Postgres v7.4 and restored on v8.1.4. All of the tables restored except three. The tables were created, but their data wasn't applied. I can see the tables in the dump file, and no errors were reported in the restore. What am I missing plea
Many thanks to all of you that helped with this.
On 7/18/06, Scott Marlowe <[EMAIL PROTECTED]> wrote:
On Sat, 2006-07-15 at 02:37, adey wrote:> Please advise if there is a way to start a fresh Postgresql error /
> output log at regular intervals?> We are tuning a "new toproduction" system, so I hav
Title: Restarting PostgreSQL
Hi,
If u have all your data's not try to start
initdb just try using /usr/local/pgsql/bin/pg_ctl -D /usr/local/psql/data
start
Thanks & RegardsDilipkumar
- Original Message -
From:
Rojas, Fernando
(CIAT)
To: pgsql-admin@postgresql.org
15 matches
Mail list logo