Re: db commands elicit no response

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Fred Parkinson <FredP(at)abag(dot)ca(dot)gov>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: db commands elicit no response
Date: 2016-02-24 18:20:03
Message-ID: CAKFQuwYXtdUJ3RF4gn=2nnF9+US+8C96hbFdLFRQSweUHn69ag@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Wednesday, February 24, 2016, Fred Parkinson <FredP(at)abag(dot)ca(dot)gov> wrote:

> I must be doing something stupid but I can't figure it out.
>
> **I logged into our database server (8.4.17) and did the following:
> psql template1 **to get in
> CREATE DATABASE planning_services **database created
> **logged out of template1
> psql planning_services **now in planing_services database with prompt
> planning_services(#
>

This prompt indicates that you are in line-continuation mode. Don't know
how you got there but everything you are typing is being added to a command
buffer.

> create table policies (
> "id" serial primary key,
> "description" varchar(100)
> ;
>

So, you have an open parentheses here but never closed it...which would
explain the above.

David J.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Fred Parkinson 2016-02-24 18:23:58 Re: db commands elicit no response
Previous Message Fred Parkinson 2016-02-24 18:14:32 db commands elicit no response