On Sun, Jul 31, 2005 at 06:34:47PM +0200, Stephan Meyen wrote:
} I installed postgresql (7.4.7) on a Debian testing (PowerPC). I'm going
} to use embedded SQL. I found the ecpg libraries as well as the headers,
} but I cannot find any program to precompiele my *.pgc files. The
} Postgres doc
Hello,
I installed postgresql (7.4.7) on a Debian testing (PowerPC). I'm going
to use embedded SQL. I found the ecpg libraries as well as the headers,
but I cannot find any program to precompiele my *.pgc files. The
Postgres docs say that a program called 'ecpg' should come with a
On (18/07/05 09:05), Lance Hoffmeyer wrote:
> What am I doing wrong here?
> I am not able to do anything with my postgresql database?
>
> in /etc/postgresql/pg_hba.conf
>
> local allpostgres md5
> host allpos
What am I doing wrong here?
I am not able to do anything with my postgresql database?
in /etc/postgresql/pg_hba.conf
local allpostgres md5
host allpostgres 127.0.0.1 255.255.255.255 md5
I login to a console as postgres
for <[EMAIL PROTECTED]>; Thu, 26 Aug 2004 18:15:26 +0100
Subject: Re: postgres phpgroupware login woes
From: Oliver Elphick <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: Lance Hoffmeyer <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PRO
On Thu, 2004-08-26 at 05:30, Lance Hoffmeyer wrote:
> Running SARGE. I have everything installed
> and appears to be installed correctly. If
> I login as user postgres I can login to
> a database phpgroupware. If I am any other
> user and I run command
>
> psql phpgro
Running SARGE. I have everything installed
and appears to be installed correctly. If
I login as user postgres I can login to
a database phpgroupware. If I am any other
user and I run command
psql phpgroupware -U postgres -W
I get error
psql: FATAL: IDENT authentication failed for user
On Sat, 26 Jun 2004 01:20:56 -0400, Mark Roach
> apt-get source gnucash
> apt-get build-dep gnucash
> cd gnucash-{version}
> $EDITOR debian/rules # (here you should modify the line that runs ./
> configure and add the appropriate switches)
> dpkg-buildpackage
And insta
On Fri, 2004-06-25 at 10:49 +0200, Berteun Damman wrote:
[...]
> But, I'd really like to make use of the postgres backend (I did so
> until last week, when I switched from Gentoo back to Debian, without
> any serious problems). Is there some place where the postgres backend
>
Hello,
I discovered Debian's Gnucash does not provide the Postgres backend,
because it is being revamped to support all of Gnucash' features.
However, it seems to me that this process isn't really getting on.
But, I'd really like to make use of the postgres backend (I di
On Tue, 2004-05-25 at 02:36, Tom Allison wrote:
> So the "tcpip_socket=yes" statement has nothing to do with TCP/IP
> connection? While tcpip_sockets=no is the default from postgres, the
> configuration file in Debian shows otherwise.
tcpip_socket=yes makes the postmaste
ocket.
So the "tcpip_socket=yes" statement has nothing to do with TCP/IP
connection? While tcpip_sockets=no is the default from postgres, the
configuration file in Debian shows otherwise.
However, it is not accessible from any other network address (sockets
and localhost only).
And other
On Sun, May 23, 2004 at 14:46:34 -0400, Tom Allison wrote:
> J.H.M. Dassen (Ray) wrote:
> >PostgreSQL doesn't care about /etc/passwd. The default client
> >authentication settings care about what user is connecting to the
> >database server through a UNIX socket.
> Gee I must have missed something
ed in both
the /etc/passwd file and the postgres database.
No. It implies you haven't set PostgreSQL's client authentication settings
to ones you like.
Or does postgres just us the /etc/passwd file for all of it's
authentications?
PostgreSQL doesn't care about /etc/passwd
pgsql listed in both
> the /etc/passwd file and the postgres database.
No. It implies you haven't set PostgreSQL's client authentication settings
to ones you like.
> Or does postgres just us the /etc/passwd file for all of it's
> authentications?
PostgreSQL doesn't care
On Sat, 2004-05-22 at 22:19, Tom Allison wrote:
> I'm doing a -testing installation of postgresql.
>
> I have the user postgres in the passwd file.
> I don't know what the password is.
>
> I'm wondering:
>
> Should I know it? I can always su posgres f
stuck.
I created a user in psql but now I can't log in as that user.
I get an error
psql: FATAL: IDENT authentication failed for user "dbmail"
This implies that I need to have all my users for pgsql listed in both
the /etc/passwd file and the postgres database. Or does postgr
I'm doing a -testing installation of postgresql.
I have the user postgres in the passwd file.
I don't know what the password is.
I'm wondering:
Should I know it? I can always su posgres from root, but I don't always
want to have to go root first. Is there is any problems
On Wed, Feb 18, 2004 at 12:36:55PM -0500, Danny O'Brien wrote:
> According to research, it seems as though we failed to compile PHP with
> postgres support at install time. We used Debian packages to install
> PHP and don't recall whether compiling with postgres was an option.
We've been getting the following error when testing our PHP pages that make calls to our postgres database:
Fatal error: Call to undefined function: pg_pconnect() in /var/www/.php on line 14
According to research, it seems as though we failed to compile PHP with postgres support at install
just for kicks - try "su - postgres" - seems to work for me
Glenn
On Sun, 2004-01-18 at 10:25, Christoph Bühring wrote:
> Hi,
> I´ve got following Problem:
>
> initdb: cannot be run as root
> Please log in (using, e.g., "su") as the (unprivileged) us
Hi,
I´ve got following Problem:
initdb: cannot be run as root
Please log in (using, e.g., "su") as the (unprivileged) user that will
own the server process.
I´m using an unstable Debian System. The error appears with postgres-
/stable/unstable and testing Vers
On Mon, 12 Jan 2004 02:14:14 +, Oliver Elphick wrote:
> On Sun, 2004-01-11 at 09:27, Paul Morgan wrote:
>> I've been following this thread with interest, being a user of postgreql
>> 7.3.4 on sarge, as the upgrade will be heading my way soon. I did wonder
>> why the postinstall on your first
e are in the
old package, which has already been deleted by the time the new postinst
can attempt to do the upgrade. So the binaries are copied to
/var/lib/postgres/dumpall/7.3/ by the prerm of the old packages, but
this is done only if there is no copy already there (this was because we
could end up
On Sunday 11 January 2004 09:27, Paul Morgan wrote:
> On Sun, 11 Jan 2004 00:14:45 +, Richard Lyons wrote:
> > On Saturday 10 January 2004 01:08, Oliver Elphick wrote:
> >
> > [...snipped: details of stupidly upgrading postgres
> > without first doing
On Sun, 11 Jan 2004 00:14:45 +, Richard Lyons wrote:
> On Saturday 10 January 2004 01:08, Oliver Elphick wrote:
>
> [...snipped: details of stupidly upgrading postgres
> without first doing pg_dumpall, causing need to
> downgrade from 7.4 to 7.3 temporarily..
On Saturday 10 January 2004 01:08, Oliver Elphick wrote:
[...snipped: details of stupidly upgrading postgres
without first doing pg_dumpall, causing need to
downgrade from 7.4 to 7.3 temporarily...]
> Use --force-depends and --force-conflicts.
>
Just in case it helps the
Hello Richard!
On Sat, Jan 10, 2004 at 12:35:13AM +, Richard Lyons wrote:
I went to ftp://ftp.debian.org/debian/pool/main/p/postgresql/
and got postgresql-client and postgresql, both 7.3.4-9. Then this is
what happened:
---
dpkg -i /home/richard/files/temp/postgres*.deb
es, thanks again Monique, I have quite muddled this thread with
> adding to my own postings. That was what Nicos Gollan suggested a few
> hours earlier, and I reported my failure in a different post. I'll
> repeat it for simplicity:
Ah, sorry, of course you posted that earlier.
Wel
On Sat, 2004-01-10 at 00:35, Richard Lyons wrote:
> I went to
> ftp://ftp.debian.org/debian/pool/main/p/postgresql/
> and got postgresql-client and postgresql, both 7.3.4-9. Then this is
> what happened:
> ---
> dpkg -i /home/richard/files/
lan suggested a few hours
earlier, and I reported my failure in a different post. I'll repeat it
for simplicity:
I went to
ftp://ftp.debian.org/debian/pool/main/p/postgresql/
and got postgresql-client and postgresql, both 7.3.4-9. Then this is
what happened:
---
On Wed, 2004-01-07 at 23:21, Monique Y. Herman wrote:
> How important is it to run the default-install do.maintenance cron job
> if you're running autovacuum? Should I just get rid of it?
>
> Since my last upgrade of postgres on unstable, I've received the
> following
On 2004-01-09, Richard Lyons penned:
> On Friday 09 January 2004 16:19, Richard Lyons wrote:
>> On Friday 09 January 2004 15:02, Nicos Gollan wrote:
>> > On Fri, 9 Jan 2004 14:24:33 +
>> >
>> > Richard Lyons <[EMAIL PROTECTED]> wrote:
>> > > Running sid. postgresql is now 7.4, but won't open
On Friday 09 January 2004 16:19, Richard Lyons wrote:
> On Friday 09 January 2004 15:02, Nicos Gollan wrote:
> > On Fri, 9 Jan 2004 14:24:33 +
> >
> > Richard Lyons <[EMAIL PROTECTED]> wrote:
> > > Running sid. postgresql is now 7.4, but won't open until I
> > > upgrade the database, which I
and see if that would cure
> > the printing. (it didn't).
> >
> > But I forgot to check whether postgres would be upgraded and it
> > was. Now I cannot access my database.
> >
> > Running sid. postgresql is now 7.4, but won't open until I
> > upg
; But I forgot to check whether postgres would be upgraded and it was.
> Now I cannot access my database.
>
> Running sid. postgresql is now 7.4, but won't open until I upgrade
> the database, which I can't without 7.3. What do I do?
>
You know, I got this same error afte
ackages at
> ftp://ftp.debian.org/debian/pool/main/p/postgresql/
> and install with dpkg.
this is what happened:
---
dpkg -i /home/richard/files/temp/postgres*.deb
dpkg - warning: downgrading postgresql-client from 7.4.1-1 to 7.3.4-9.
(Reading database ... 148728 files
On Friday 09 January 2004 15:02, Nicos Gollan wrote:
> On Fri, 9 Jan 2004 14:24:33 +
>
> Richard Lyons <[EMAIL PROTECTED]> wrote:
> > Running sid. postgresql is now 7.4, but won't open until I
> > upgrade the database, which I can't without 7.3. What do I do?
>
> You can specify a version wh
Em Sex, 2004-01-09 Ãs 12:24, Richard Lyons escreveu:
> Running sid. postgresql is now 7.4, but won't open until I upgrade the
> database, which I can't without 7.3. What do I do?
You can put testing in your sources.list, and apt-get update; apt-get
-t testing install postgresql. If no
On Fri, 9 Jan 2004 14:24:33 +
Richard Lyons <[EMAIL PROTECTED]> wrote:
> Running sid. postgresql is now 7.4, but won't open until I upgrade
> the database, which I can't without 7.3. What do I do?
You can specify a version when calling apt-get, read the manpage for
info on that.
You can a
Stupid me! I have cups problems and that foomatic bug. Some apps print
the wrong way round on the sheet, so I did an upgrade via aptitude to
get the debugged foomatic and see if that would cure the printing. (it
didn't).
But I forgot to check whether postgres would be upgraded and i
How important is it to run the default-install do.maintenance cron job
if you're running autovacuum? Should I just get rid of it?
Since my last upgrade of postgres on unstable, I've received the
following email several times a day:
Subject: Cron <[EMAIL PROTECTED]> /usr/bin/
Oliver Elphick <[EMAIL PROTECTED]> wrote:
>> reason for this behaviour?
>
> pg_autovacuum (from postgresql-contrib) is started by
> /etc/init.d/postgresql (if so configured by
> /etc/postgresql/postmaster.conf). It is turned on by default.
>
> --
> Oliver Elphick[
On Tue, 2004-01-06 at 18:16, outsider wrote:
> Hi!
> After an upgrade from postgres 7.3 to postgres 7.4 I see every 5 minutes
> in the /var/syslog messages like
> ---
> connection: Host=[local] Port=
> user=postgres
> ---
> postgres connects every 5 minutes to each data
On Tue, Jan 06, 2004 at 07:16:24PM +0100, outsider wrote:
> After an upgrade from postgres 7.3 to postgres 7.4 I see every 5
minutes
> in the /var/syslog messages like
> ---
> connection: Host=[local] Port=
> user=postgres
> ---
> postgres connects every 5 minutes to each
Hi!
After an upgrade from postgres 7.3 to postgres 7.4 I see every 5 minutes
in the /var/syslog messages like
---
connection: Host=[local] Port=
user=postgres
---
postgres connects every 5 minutes to each database I have. What is the
reason for this behaviour?
I'm using Debian SID.
Thank y
On Mon, 22 Dec 2003 16:04:05 -0700, Monique Y. Herman wrote:
>
> Thank you so much! This is exactly what I was looking for, and your
> example made it very easy to understand.
My pleasure. I'm not that good at much, but I'm fairly good with SQL
stuff.
--
paul
Guy: "Would
On Mon, 22 Dec 2003 at 21:30 GMT, Paul Morgan penned:
>
> Monique, you're using the to_date function the wrong way round, which is
> not an uncommon mistake.
>
> to_date() converts a string to a date, *not* a date to a string. So your
> working example works because to_date() is taking the strin
On Mon, 22 Dec 2003 at 22:28 GMT, Pablo Aguiar penned:
> On Sun, 21 Dec 2003 20:34:28 -0700 "Monique Y. Herman"
> <[EMAIL PROTECTED]> wrote:
>
>> Summary: attempting to use to_date on a table value results in a
>> to_timestamp error. What am I doing wrong?
>
> You have to tell PostgreSQL the for
On Sun, 21 Dec 2003 20:34:28 -0700, Monique Y. Herman wrote:
> I know this isn't the postgres user group, but if anyone has any
> insight, I'd sure appreciate it.
>
> Summary: attempting to use to_date on a table value results in a
> to_timestamp error. What am I d
to to_timestamp (or to to_date) by parameter.
If you say 'DD Mon ' by the 2nd param then postgre will expect
something like '22 Dez 2003' as the 1st param.
But according to your postgres.conf, when you select a date postgres
returns something in the format '-MM-DD
I know this isn't the postgres user group, but if anyone has any
insight, I'd sure appreciate it.
Summary: attempting to use to_date on a table value results in a
to_timestamp error. What am I doing wrong?
I have a little database and want to prettyprint some dates on the web
inte
On Thu, 2003-11-20 at 16:23, Monique Y. Herman wrote:
> On Thu, 20 Nov 2003 at 02:50 GMT, Henry Hollenberg penned:
> > Hello,
> >
> > I have a database running on potato using postgres 6.5 that I'd like
> > to upgrade to Woody running postgres 7.2.
...
> I belie
On Thu, 20 Nov 2003 at 02:50 GMT, Henry Hollenberg penned:
> Hello,
>
> I have a database running on potato using postgres 6.5 that I'd like
> to upgrade to Woody running postgres 7.2.
>
> The docs seem to imply that upgrading with this big a jump from 6.5 to
> 7.2 is
On Wed, Nov 19, 2003 at 06:50:19PM -0800, Henry Hollenberg wrote:
> The docs seem to imply that upgrading with this big a jump from
> 6.5 to 7.2 is dangerous.even if I do it by hand like so:
>
> pg_dump mydatabase > dump.mydatabase
> destroydb mydatabase
> upgrade the database system to 7.2
>
Hello,
I have a database running on potato using postgres 6.5 that I'd like to upgrade to
Woody running postgres 7.2.
The docs seem to imply that upgrading with this big a jump from 6.5 to 7.2 is
dangerous.even if I do it by hand like so:
pg_dump mydatabase > dump.mydatabase
d
Hello,
I have a database running on potato using postgres 6.5 that
I'd like to upgrade to Woody running postgres 7.2.
The docs seem to imply that upgrading with this big a jump from
6.5 to 7.2 is dangerous.even if I do it by hand like so:
pg_dump mydatabase > dump.mydatabase
d
e existing process).
Then I tried the -x business. -e was already set; I tried running
preinst with both "set -ex" and "set -e" and "set -x". Both ways, the
script actually completed and exited with return code 0. I also tried
running the script with argument "u
On Sat, 2003-10-11 at 06:39, Monique Y. Herman wrote:
> home:/var/lib/dpkg/info# apt-get install postgresql
...
> Preconfiguring packages ...
> (Reading database ... 76051 files and directories currently installed.)
> Unpacking postgresql (from .../postgresql_7.3.4-6_i386.deb) ...
> dpkg: error pro
Time to admit the sorry truth ... at the time that I switched from RH to
Debian several years ago, my Debian install's version of postgres was
older than the version I'd compiled on RH, and consequently I had to
install from source to get postgres 7.0 functionality.
I um ... *blush* .
Unable to connect to PostgreSQL server: FATAL 1: IDENT
> authentication failed for user "dan" in /var/www/boards/db/postgres7.php
> on line 79
> phpBB : Critical Error
>
> Could not connect to the database
...
> Postgres as well as all the web services required are.
>
>
tabase
>
> which would lead someone to think that Postgres is not running,
No. It should lead someone to think that Postgres is running, but is
refusing the connection attempt on the basis of its access control settings
in /etc/postgresql/pg_hba.conf; possibly because you haven't in
n" in /var/www/boards/db/postgres7.php
on line 79
phpBB : Critical Error
Could not connect to the database
which would lead someone to think that Postgres is not running, however
as nmap clearly shows :
[EMAIL PROTECTED]:~$ nmap intermission
Starting nmap 3.45 ( http://www.insecure.org/nmap/
On Wed, Jan 15, 2003 at 10:34:27AM -0600, will trillich wrote:
> Active System Attack Alerts
> =-=-=-=-=-=-=-=-=-=-=-=-=-=
> Jan 15 08:32:17 server postgres[6712]: [2-2] Nested Loop (cost=1.77..13992.25 rows=1
>width=101)
> Jan 15 08:32:17 server postgres[6712]: [2-3] -> Nest
well my adrenals got their exercise today. i'm wondering what's
the best approach -- munge logcheck? munge postgres?
here's logcheck sent me:
Active System Attack Alerts
=-=-=-=-=-=-=-=-=-=-=-=-=-=
Jan 15 08:32:17 server postgres[6712]: [2-2] Nested Loop (cost=1.77..13992.25 ro
On Tue, Dec 31, 2002 at 05:14:52PM +0530, Sandip P Deshmukh wrote:
> when i run setup_beancounter, it says, no postgressql user 'sandip'. it
> also recommends me to su - postgres.
>
> when i do this, neither my root password nor my user password works!
> what am i doin
hello all
recently i added a beancounter package.
when i run setup_beancounter, it says, no postgressql user 'sandip'. it
also recommends me to su - postgres.
when i do this, neither my root password nor my user password works!
what am i doing that is incorrect?
--
regards,
On Thu, Dec 05, 2002 at 05:26:33PM +0100, Bruno Boettcher wrote:
> Hello
>
> i got used to the automatic postgres upgrade... and stopped making
> myself dumps before upgrading... :(
>
> and now i am stuck.. the automatic upgrade failed, and i don't know
> how
On Thu, Dec 05, 2002 at 07:48:41PM -0600, Hank Marquardt wrote:
> My first apt-get upgrade that bumped postgres to 7.3 didn't auto update,
> so I was futzing with a manual upgrade and it wasn't working, so since I
> had a recent dump of the data and it's not a pro
My first apt-get upgrade that bumped postgres to 7.3 didn't auto update,
so I was futzing with a manual upgrade and it wasn't working, so since I
had a recent dump of the data and it's not a production machine (it's my
workstation) I tried using uninstalling the package (dpkg
Hello
i got used to the automatic postgres upgrade... and stopped making
myself dumps before upgrading... :(
and now i am stuck.. the automatic upgrade failed, and i don't know
how to get this back...
i tried the migration file, but couldn't get something usable out of
it...
>
> I can't for the life of me get postgresql to start and stop. running
> /etc/init.d/postgresql stop gets me this:
>
> Stopping PostgreSQL database: postmaster
> /etc/init.d/postgresql: command not found
>
> while running
> /usr/lib/postgresql/bin/pg_c
nd stop. running
> /etc/init.d/postgresql stop gets me this:
>
> Stopping PostgreSQL database: postmaster
> /etc/init.d/postgresql: start-stop-daemon: command not found
>
> while running
> /usr/lib/postgresql/bin/pg_ctl-D /var/lib/postgres/data stop
> gives the following:
>
d/postgresql: start-stop-daemon: command not found
while running
/usr/lib/postgresql/bin/pg_ctl-D /var/lib/postgres/data stop
gives the following:
pg_ctl: cannot find /var/lib/postgres/data/postmaster.pid
Is postmaster running?
I guess I'm missing something important, but it's
On Wed, Oct 09, 2002 at 02:22:38AM -0400, Matt Price wrote:
> localall trust
> host all 127.0.0.1 255.0.0.0 ident
Here you tell PostgreSQL to use ident.
> ps: assuming I get thisworking, how do I add other database
like this (slightly modified from the
original):
[PostgreSQL]
Description = PostgreSQL template1
Driver = PostgreSQL
Trace = No
TraceFile = /tmp/odbc.log
Database= template1
Servername = localhost
UserName
md5
host all 0.0.0.0 0.0.0.0 reject
why would tora give such an error? (btw I tried to type everything
few times to make sure there's no typo/capslock on etc.)
this is on debian unstable, postgres 7.2.2-2, tora 1.3.7-4.
any ideas?
TIA!
On Thu, 2002-09-26 at 08:51, Erik Steffl wrote:
>I get the following error message when trying to connect to postgres
> using tora:
>
> No pg_hba.conf entry for host...
>
>I think that the settings are ok since I can loging using psql:
>
> jojda:~> psql poku
I get the following error message when trying to connect to postgres
using tora:
No pg_hba.conf entry for host...
I think that the settings are ok since I can loging using psql:
jojda:~> psql pokus -U erik -W
Password:
Welcome to psql, the PostgreSQL interactive terminal.
here&#
Sent: den 18 september 2002 09:00
To: [EMAIL PROTECTED]
Subject: Re: apt-get source postgres
On Wed, 2002-09-18 at 05:49, Jonas Persson wrote:
> Hi everyone, i have a problem finding postgresql 7.1.3 source as debian package. I
>looked in potato
> but there the version is 6.5.4. The rea
working properly.
Hmmm, not even snapshots.debian.net has 7.1.3 pkgs, from what I can see.
Are you sure you don't want to upgrade the application? 7.2 has
improvements and bugfixes (a few of them quite important), so if your
application should run for some time it would probably be worth it.
You could try ma
Hi everyone, i have a problem finding postgresql 7.1.3 source as debian package. I
looked in potato
but there the version is 6.5.4. The reason why i want an older version is that the
application i want to
run against postgresql uses features which is changed in 7.2 and will make the
applicati
On 0, stan <[EMAIL PROTECTED]> wrote:
> I'm going to set up some databases for various personal use (household
> itmems, books, music, et all) using porgres for the db.
>
> This will be done on a woody machine.
>
> Cany anyone recomend ood tools for dat input forms & reports> I'm thinking
> of
I'm going to set up some databases for various personal use (household
itmems, books, music, et all) using porgres for the db.
This will be done on a woody machine.
Cany anyone recomend ood tools for dat input forms & reports> I'm thinking
of something like Oracles forms fro the input/edit side
On Mon, 2002-04-22 at 03:17, Andreas Goesele wrote:
...
> You are now connected to database template1 as user postgres.
> CREATE DATABASE "accounts" WITH TEMPLATE = template0 ENCODING = 'LATIN1';
> ERROR: CREATE DATABASE: database "accounts" already exi
Jason Chambers <[EMAIL PROTECTED]> writes:
> > CREATE USER "user" WITH SYSID 1 CREATEDB CREATEUSER;
> > ERROR: CREATE USER: sysid 1 is already assigned
> ^^^
>
> Sysid 1 is probably assigned to the user post
to call the users as one likes?
Anyway how can I get my postgres databases again working?
Problem in some more details:
During the upgrade I opted for the automatic upgrade. I was shown a
beautiful db.out and continued.
But then something went wrong, and I can't connect, getting instead
the
es?
Anyway how can I get my postgres databases again working?
Problem in some more details:
During the upgrade I opted for the automatic upgrade. I was shown a
beautiful db.out and continued.
But then something went wrong, and I can't connect, getting instead
the error message:
psql: FATAL
db.out is right up to date:
$ su
# su - postgres
$ psql -d template1 < db.out
--
Oliver Elphick[EMAIL PROTECTED]
Isle of Wight http://www.lfix.co.uk/oliver
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C
&q
I tried to upgrade php4-pgsql and ended up having to upgrade the database.
I ended the postgresql-dump early and all I have is a saved.data directory
and a db.out file. How do I recreate my database from one of these?
Lance
--
Lance Hoffmeyer
On Thu, 2002-02-28 at 21:38, Andreas Goesele wrote:
> I also have debug_level = 0 in postgresql.conf believing that this
> would stop all debugging massages, but this is not the case. My
> console gets flooded by messages of the type: DEBUG: ...
>
> Is there any way I can effectively st
Hi,
with the help of people on this list (Thanks Martin and Brooks!) I
freed my syslog from all those debugging messages. But as I have (as
recommended) silent_mode = off in postgresql.conf my console still
gets cluttered by all those debugging messages.
I also have debug_level = 0 in postgresq
Hi Andreas!
On Mon, 18 Feb 2002, Andreas Goesele wrote:
> thanks to help from this list I now finally have successfully upgraded
> to postgresql 7.1.
>
> But now my syslog gets to much logging from postgres. In
> postgresql.conf I have:
>
> debug_level = 0
> log_c
| But now my syslog gets to much logging from postgres. In
| postgresql.conf I have:
|
| debug_level = 0
| log_connections = on
| log_pid = on
| log_timestamp = on
| syslog = 2
| # if syslog is 0, turn silent_mode off!
| silent_mode = off
| syslog_facility = LOCAL0
| trace_notify = off
Try these
Hi,
thanks to help from this list I now finally have successfully upgraded
to postgresql 7.1.
But now my syslog gets to much logging from postgres. In
postgresql.conf I have:
debug_level = 0
log_connections = on
log_pid = on
log_timestamp = on
syslog = 2
# if syslog is 0, turn silent_mode off
Andreas Goesele <[EMAIL PROTECTED]> writes:
> "J.H.M. Dassen (Ray)" <[EMAIL PROTECTED]> writes:
>
> > Switch back to the pg_hba.conf file you used with 6.5. 7.1 has a new
> > authentication method "peer" which 6.5 doesn't understand and which 7.1's
> > default configuration employs IIRC.
>
> Thi
"J.H.M. Dassen (Ray)" <[EMAIL PROTECTED]> writes:
> Switch back to the pg_hba.conf file you used with 6.5. 7.1 has a new
> authentication method "peer" which 6.5 doesn't understand and which 7.1's
> default configuration employs IIRC.
This helped. Thanks. But now I have a new problem: The encodin
d restarting the postmaster
> > /usr/lib/postgresql/dumpall/6.5/postmaster -D /var/lib/postgres/data -p
> > 5431 -o -d0
> > Dumping the database to db.out
> > process_hba_record: invalid syntax in pg_hba.conf file
>
> Switch back to the pg_hba.conf file you used wit
;user" as a database name.
> So I did read README.Debian.migration.gz and then run postgresql-dump
> with the options in the README. This is what I got:
>
> Stopping and restarting the postmaster
> /usr/lib/postgresql/dumpall/6.5/postmaster -D /var/lib/postgres/data -p 5431
> -o -d0
>
So I did read README.Debian.migration.gz and then run postgresql-dump
with the options in the README. This is what I got:
Stopping and restarting the postmaster
/usr/lib/postgresql/dumpall/6.5/postmaster -D /var/lib/postgres/data -p 5431
-o -d0
Dumping the database to db.out
process_hba_record:
101 - 200 of 330 matches
Mail list logo
