On Thu, Aug 27, 2015 at 4:19 PM, Abraham Mathew
wrote:
"test" is not in the postgres database. In fact, there is no table or
column named "test"
The user is "postgres" and the dbname is also "postgres"
On Thu, Aug 27, 2015 at 4:13 PM, John McKown
wrote:
> On Thu, Aug 27, 2015 at 3:50 PM, Ab
On Thu, Aug 27, 2015 at 3:50 PM, Abraham Mathew
wrote:
>
> Yeah, thought that could be an issue. Unfortunately, I've had issues
> setting a normal user id and then having postgres identify the password
> associated with it. Using postgres was the only thing that worked.
>
> ## CONNECT TO LOCALHOS
On 08/27/2015 01:38 PM, Tom Lane wrote:
Adrian Klaver writes:
I am seeing something I cannot figure out when using psql.
This is what I see:
psql (9.4.4)
Type "help" for help.
production_5432=> select from cell_per ;
--
(56 rows)
I believe this is the expected output for a table with
Adrian Klaver writes:
> I am seeing something I cannot figure out when using psql.
> This is what I see:
> psql (9.4.4)
> Type "help" for help.
> production_5432=> select from cell_per ;
> --
> (56 rows)
I believe this is the expected output for a table with 56 rows and zero
columns. (It's pr
Postgres 9.4.4.
I am seeing something I cannot figure out when using psql.
This is what I see:
psql (9.4.4)
Type "help" for help.
production_5432=> select from cell_per ;
--
(56 rows)
This is when I am logged in as system user aklaver. If I log in as
another user on the same machine I see t
On 08/27/2015 10:46 AM, Ryan King - NOAA Affiliate wrote:
When attempting to create the required functions and extensions for the
MySQL FDW, I get the following errors:
dbname=# CREATE FUNCTION mysql_fdw_handler()
RETURNS fdw_handler
AS '$libdir/mysql_fdw'
LANGUAGE C STRICT;
ERROR: could not a
David Nelson writes:
>>> So in the UPDATE statement, I only provided a value for last_user. But the
>>> first test of the trigger function tests for a NULL value of
>>> NEW.empname. Since
>>> I did not provide one, I was expecting it to be NULL and an exception to
>>> be thrown. Am I just misunde
When attempting to create the required functions and extensions for the
MySQL FDW, I get the following errors:
dbname=# CREATE FUNCTION mysql_fdw_handler()
RETURNS fdw_handler
AS '$libdir/mysql_fdw'
LANGUAGE C STRICT;
ERROR: could not access file "$libdir/mysql_fdw": No such file or directory
d
On 08/27/2015 06:47 AM, ss wrote:
I have started writting query since a day on postGreS my query is :
CREATE TABLE IF NOT EXISTS utilisateurs (
SEQU_NK SERIAL PRIMARY KEY NOT NULL UNIQUE,
UTILISATEUR_NK bigint NOT NULL,
NOM varchar(25) COLLATE latin1_general_ci NOT NU
I have started writting query since a day on postGreS my query is :
CREATE TABLE IF NOT EXISTS utilisateurs (
SEQU_NK SERIAL PRIMARY KEY NOT NULL UNIQUE,
UTILISATEUR_NK bigint NOT NULL,
NOM varchar(25) COLLATE latin1_general_ci NOT NULL DEFAULT '',
PASSE varchar(40) C
On 8/26/2015 11:55 PM, Nima Azizzadeh wrote:
Hello,
I'm going to create two factor authentication for pgadmin server...
you mean postgresql server, don't you? pgadmin is a client program/utility.
I'm using postgresql 9.4 with pgadmin III on Linux Mint 17.2 32bit...
I already have 1 password
>> So in the UPDATE statement, I only provided a value for last_user. But
the
>> first test of the trigger function tests for a NULL value of
>> NEW.empname. Since
>> I did not provide one, I was expecting it to be NULL and an exception to
>> be thrown. Am I just misunderstanding how things work? I
What exactly does bdr_node_wait_for_ready() do? I've been trying to setup
BDR on an existing database and once I run the select
bdr.bdr_node_wait_for_ready(); command on the 2nd node after running the
bdr.bdr_group_join() command it just hangs . I've done the same setup
procedure on brand new nod
On 08/27/2015 09:07 AM, David Nelson wrote:
Good morning all,
I am creating an updatable view on a set of tables, and just ran into
unexpected (or more likely misunderstood) behavior with the UPDATE
statement. If an attribute is not explicitly listed in the UPDATE statement,
the NEW value appear
Good morning all,
I am creating an updatable view on a set of tables, and just ran into
unexpected (or more likely misunderstood) behavior with the UPDATE
statement. If an attribute is not explicitly listed in the UPDATE statement,
the NEW value appears to be populated with the OLD value. Unless I
Ray Stell wrote:
> Is there an preferred BDR? Should there be a mailing-list?
This is the list for BDR questions.
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-general mailing list (pgsql-g
Is there an preferred BDR? Should there be a mailing-list?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On 08/27/2015 06:33 AM, Christopher BROWN wrote:
Hello Adrian,
Yep, Charles' explanation helped me understand what was going on.
Before that, I was as confused as you were (in your first reply) about
how access_mode could be NULL (with the same reasoning). In any case,
thanks for your links ; I
Hi
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of Adrian Klaver
> Sent: Donnerstag, 27. August 2015 15:41
> To: Christopher BROWN
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Strange TRIGGER failur
On 08/27/2015 06:33 AM, Christopher BROWN wrote:
Hello Adrian,
Yep, Charles' explanation helped me understand what was going on.
Before that, I was as confused as you were (in your first reply) about
how access_mode could be NULL (with the same reasoning). In any case,
thanks for your links ; I
Hello Adrian,
Yep, Charles' explanation helped me understand what was going on. Before
that, I was as confused as you were (in your first reply) about how
access_mode could be NULL (with the same reasoning). In any case, thanks
for your links ; I did try searching the web for the answer before p
Hello Charles,
Your first suggestion effectively matches what I did as a workaround, with
the advantage that your suggestion explicitly orders the columns and has an
explanation attached... and your second suggestion seems to match what I
was originally trying to do.
I was, perhaps naively, tryin
On 08/27/2015 04:49 AM, Christopher BROWN wrote:
Hello,
I'm new to this list but have been using PostgreSQL for a moment. I've
encountered an error using PostgreSQL 9.4.4 which can be reproduced
using the SQL below.
The trigger "init_store_ldap_profiles_trigger" fails if the function
"init_sto
On 08/27/2015 04:49 AM, Christopher BROWN wrote:
Hello,
I'm new to this list but have been using PostgreSQL for a moment. I've
encountered an error using PostgreSQL 9.4.4 which can be reproduced
using the SQL below.
The trigger "init_store_ldap_profiles_trigger" fails if the function
"init_sto
Another possibility is
CREATE OR REPLACE FUNCTION init_store_ldap_profiles() RETURNS TRIGGER AS $$
DECLARE
r RECORD;
BEGIN
FOR r IN
SELECT id, ref_ldap_department, ref_ldap_title, access_mode FROM
application.store_ldap_profile_defaults WHERE format = NEW.format
Hello
You declare your variable r as of type
application.store_ldap_profile_defaults%rowtype, but then select only 4 of the
5 fields of the table to put in there. The last one (happens to be access_mode
is then null).
The structures don’t match. That may explain this behaviour.
This wor
Hello,
I'm new to this list but have been using PostgreSQL for a moment. I've
encountered an error using PostgreSQL 9.4.4 which can be reproduced using
the SQL below.
The trigger "init_store_ldap_profiles_trigger" fails if the function
"init_store_ldap_profiles()" is written as below. If I rewr
Adrian Klaver writes:
> Best guess, since this is a laptop, the network is not connected until
> NetworkManager(or something similar) is active. On my laptop that
> happens late in the startup sequence, after Postgres starts. This is
> especially true if you are connecting to a wireless AP.
I ca
28 matches
Mail list logo
