On Tue, Dec 10, 2013 at 06:25:16PM -0800, Gary Roach wrote:
automatically (I think). I found the Debian README confusing,
especially in regards to setting up a special shell that I don't
think I need.
Are you referring to the postgres user?
--
If you're not careful, the newspapers will have
On 12/10/2013 11:13 PM, Raffaele Morelli wrote:
2013/12/11 Gary Roach gary719_li...@verizon.net
mailto:gary719_li...@verizon.net
I just switched from using PHP and Mysql to Python / Django and
Postgresql. I am having trouble with the setup of Postgresql
permissions. I am locked out
2013/12/11 Gary Roach gary719_li...@verizon.net
On 12/10/2013 11:13 PM, Raffaele Morelli wrote:
BTW you are not clear: what are you trying to achieve?
Not too surprising that I wasn't clear. I feel like I'm floundering
around. I am trying to build a data archiving system that will have
2013/12/11 Gary Roach gary719_li...@verizon.net
I just switched from using PHP and Mysql to Python / Django and
Postgresql. I am having trouble with the setup of Postgresql permissions. I
am locked out of some parts of the system and am unsure when to use
postgres login vs user login. Most of
On Fri, Jan 30, 2009 at 10:02:01AM -0200, Eduardo M KALINOWSKI wrote:
Jude DaShiell wrote:
Okay, I figured all of it out. postgresql is uninstallable because
postgresql-common requires postgresql79 and that's uninstallable.
I'm probably feeding a troll right now (and I know I shouldn't),
Jude DaShiell wrote:
Okay, I figured all of it out. postgresql is uninstallable because
postgresql-common requires postgresql79 and that's uninstallable.
I'm probably feeding a troll right now (and I know I shouldn't), but
neither the etch nor the lenny/sid versions of 'postgresql' depend on
On Thu, Jan 29, 2009 at 04:19:40PM -0500, Jude DaShiell wrote:
I found out a little more just now. Having failed to find the debian
packager's installation instructions for postgresql I removed the
packages from this system. Later I figured to install everything and
take another look. I
Okay, I figured all of it out. postgresql is uninstallable because
postgresql-common requires postgresql79 and that's uninstallable. That
sets up a situation almost similar to what I encountered when I tried
installing emacs and gnus but at least gnus is already in the current
version of
This gets stranger by the second. I managed to get postgresql going as
user postgres with postgresql -h 127.0.0.1 cr. Then I was able to run
createuser dashielljt successfully and createdb too. So I exited the
postgres identity and dropped back to dashielljt and tried psql -h
127.0.0.1 and
On Wed, 28 Jan 2009 23:40:12 +0100, Jude DaShiell wrote:
This gets stranger by the second. I managed to get postgresql going as
user postgres with postgresql -h 127.0.0.1 cr. Then I was able to
run createuser dashielljt successfully and createdb too. So I exited
the postgres identity and
It makes no difference if you've done su - postgres before running
createuser, the same error message appears. I checked that to make sure.
I do have a firewall up and running on this machine and port 5432 is not
open to the world if that helps any.
--
To UNSUBSCRIBE, email to
I installed version 8.3.5 with tasksel. When I ran initdb, it ran in
debug mode but ran successfully so far as I can tell. I was then able to
run postgres -D /usr/local/postgresql/data and the message that came back
said postgres was ready to accept connections. I exited that and the
On Sun, 2009-01-25 at 06:04 -0500, Jude DaShiell wrote:
Script started on Sun 25 Jan 2009 05:56:42 AM EST
verizon:~# createuser dashielljt
Shall the new role be a superuser? (y/n) y
createuser: could not connect to database postgres: could not connect to
server: No such file or directory
On 01/24/2009 06:37 AM, Jude DaShiell wrote:
I managed to make the postgresql cluster with initdb but can't do
Are you *sure* that PostgreSQL is clusterable?
anything with createuser because postgresql by default is trying to use
a unix socket at address 5432. I'm running on amd hardware
14 matches
Mail list logo
