Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ehEWR-0001bq-Ea for pgsql-docs@arkaria.postgresql.org; Thu, 01 Feb 2018 13:03:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ehEWP-0004ZA-Va for pgsql-docs@arkaria.postgresql.org; Thu, 01 Feb 2018 13:03:21 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ehEWP-0004Z0-Kf for pgsql-docs@lists.postgresql.org; Thu, 01 Feb 2018 13:03:21 +0000 Received: from mail-lf0-x244.google.com ([2a00:1450:4010:c07::244]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ehEWI-00087G-H8 for pgsql-docs@lists.postgresql.org; Thu, 01 Feb 2018 13:03:20 +0000 Received: by mail-lf0-x244.google.com with SMTP id k19so26126499lfj.1 for ; Thu, 01 Feb 2018 05:03:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=mAyHAHHmVi8VHUZ9R+ptgIHVw9UgzxDDzrDYc/gAxOY=; b=VQULDsJ9K7ijo11jE2nu2jcoITPAlaq/2h8/iRbKWfYozhRUotjeIGDrFqYa2chiP4 vEatxY5oZ4qVXR948e87pcS3EU9m/91ZD+yROPgiPW1JlyDOE9AekBk93wH3ESt7T2h0 aOmD3Nh9pTIef2f+T7+xjxivex+IFuu2z94gctO65W6ZQvcNpOfWLySasB0DgDo0MK2B JWDy5V17yuqboDVWFnY2D4t3VFshFixmuYkAYCbfoHXkyO2Du2y+lQSaPLbGcNGTnr2l GvLCQ/JFftrprlHtwfGz2mXG/dv8DQDqmYZjFagMofI09Igr5Y+QveY0gmxIEUmaKTt6 2JYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:mime-version:subject:from:in-reply-to :date:content-transfer-encoding:message-id:references:to; bh=mAyHAHHmVi8VHUZ9R+ptgIHVw9UgzxDDzrDYc/gAxOY=; b=BytBL9+OgS0Fo4rDwl2qZt3IOmPXRKLHWcK+mGr2viWvCB5ZQge9i9LQJYXysyoFLh uUqBSiVIpWePukLBarxKLVtfu1QR4azrBQxEXpJu+vvWNBD4q/iOFapvZVQVvGDXoCB6 1nX3NSB+j0G+a3dIqc+49ejQqnNo+rMnxxlr/A4wCuQn0o8j6mVdmw99agrcEdPvQ67O l9bMYMNMtwiljOUsYGAvg4fuTdaiPs5fDarygNTstZT+vIFqDBhWXvvdNTyMO34CZgEo krBSGCVHGrIKmweaQUHJnoqdJLF8PNMWemuffnyDybI2L5/OYI7zhm/73ORotkQ/Pqer RAHg== X-Gm-Message-State: AKwxytf9incCTUYOTx+GU0jd70hwZGzXIu9hJO9i0dWDGaPi/R+9vf2n UrOw+8ScLdKppHc50h9Vi5c= X-Google-Smtp-Source: AH8x225Qo+COFaraV2HmMMpoDb4/Qk8xDVYPl7B3LxtBrH6CFD+f1JqzuXA7qAF4AJ6ewLsy8GRuoQ== X-Received: by 10.46.76.1 with SMTP id z1mr6213219lja.127.1517490191371; Thu, 01 Feb 2018 05:03:11 -0800 (PST) Received: from [192.168.1.69] (c-c67ce055.027-294-73746f71.cust.bredbandsbolaget.se. [85.224.124.198]) by smtp.gmail.com with ESMTPSA id t14sm1920015ljb.97.2018.02.01.05.03.10 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 01 Feb 2018 05:03:10 -0800 (PST) Sender: Daniel Gustafson Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: A simple question From: Daniel Gustafsson In-Reply-To: <151748699318.1247.28717437459073798@wrigleys.postgresql.org> Date: Thu, 1 Feb 2018 14:03:09 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <6B9C9BBA-145E-47AF-9330-50C1F553405F@yesql.se> References: <151748699318.1247.28717437459073798@wrigleys.postgresql.org> To: californiasailor@yahoo.com, pgsql-docs@lists.postgresql.org X-Mailer: Apple Mail (2.3124) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk > On 01 Feb 2018, at 13:09, PG Doc comments form = wrote: >=20 > The following documentation comment has been logged on the website: >=20 > Page: = https://www.postgresql.org/docs/9.3/static/sql-keywords-appendix.html > Description: >=20 > Hello, my client has a plethora of reserved words in their PostgreSQL > database using Greenplum. They don't wish to use the " " to allow for = them > to remain....my question is, do you have a parameter I can set to = bypass > PostgreSQL from flagging the reserved word all together? If your question concerns Greenplum and not PostgreSQL, the gpdb mailing = lists are probably a better fit: https://greenplum.org/mailing-lists/ cheers ./daniel=