Re: db commands elicit no response

From: "Fred Parkinson" <FredP(at)abag(dot)ca(dot)gov>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: db commands elicit no response
Date: 2016-02-24 18:23:58
Message-ID: 56CD84BE020000A700033475@gwia1.abag.ca.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Right you are! Somehow copy-paste lost the right-paren, put it back in and away we go!

Thanks for your prompt reply, now I can go back to work.
(I was right it was stupid)

Fred Parkinson
Application Programmer
Association of Bay Area Governments
510-464-7931

>>> On 2/24/2016 at 10:20 AM, "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
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

Browse pgsql-admin by date

  From Date Subject
Next Message drum.lucas@gmail.com 2016-02-26 04:25:48 pg_restore - Real dump file size
Previous Message David G. Johnston 2016-02-24 18:20:03 Re: db commands elicit no response