Hi William, thanks for joining the conversation.
1) We do hope for constraints since a connection to an ERP system is
possible in the future. We want to plan ahead.
2) As for the subclass approach: I would need about 30 subclasses and it
will get really hard to add new products since a change in
Thomas Munro wrote:
> On Tue, Jun 2, 2015 at 9:30 AM, Alvaro Herrera
> wrote:
> > My guess is that the file existed, and perhaps had one or more pages,
> > but the wanted page doesn't exist, so we tried to read but got 0 bytes
> > back. read() returns 0 in this case but doesn't set errno.
> >
>
On Tue, 2 Jun 2015 14:01:35 -0400
Daniel Begin wrote:
> Here is a follow-up on the step-by-step procedure proposed by PT
>
> #1 - setup postgresql planner's cost estimate settings for my hardware.
>
> --
> Curr
On Tue, Jun 2, 2015 at 9:30 AM, Alvaro Herrera wrote:
> My guess is that the file existed, and perhaps had one or more pages,
> but the wanted page doesn't exist, so we tried to read but got 0 bytes
> back. read() returns 0 in this case but doesn't set errno.
>
> I didn't find a way to set things
On 03/06/15 08:40, Andreas Ulbrich wrote:
On 02.06.2015 22:12, Melvin Davidson wrote:
Your problem is in your design.
If you do it like this:
CREATE TABLE A
(
p_col serial PRIMARY KEY,
acol integer
);
CREATE TABLE B() INHERITS (A);
INSERT INTO A(acol) VALUES (1);
INSERT INTO B(acol) VALUES
On 06/02/2015 12:33 PM, Filipe Pina wrote:
Basically, in an (maybe-over)simplified example:
CREATE OR REPLACE FUNCTION add_transaction(transaction core_transaction)
RETURNS integer AS $$
DECLARE
transaction2 core_transaction;
BEGIN
transaction.field1 := 'lapse’;
transaction2.
On 06/02/2015 11:46 AM, Tom Lane wrote:
Adrian Klaver writes:
On 06/02/2015 11:04 AM, Steve Pribyl wrote:
I have noted that "GRANT ALL ON SCHEMA public TO public" is granted
on postgres.schemas.public. I am looking at this in pgadmin so excuse
my nomenclature.
Is this what is allowing wri
> > Hm. If GetOldestMultiXactOnDisk() gets the starting point by scanning
> > the disk it'll always get one at a segment boundary, right? I'm not sure
> > that's actually ok; because the value at the beginning of the segment
> > can very well end up being a 0, as MaybeExtendOffsetSlru() will have
>
On Tue, Jun 2, 2015 at 4:19 PM, Andres Freund wrote:
> I'm not really convinced tying things closer to having done trimming is
> easier to understand than tying things to recovery having finished.
>
> E.g.
> if (did_trim)
> oldestOffset = GetOldestReferencedOffset(oldest_da
I afraid there is a bug in ALTER EVENT TRIGGER:
I run the following script:
\set ON_ERROR_ROLLBACK ON
BEGIN;
CREATE FUNCTION event_trigger_function() RETURNS event_trigger AS $$
BEGIN
RAISE NOTICE 'event_trigger_function';
END$$ LANGUAGE plPgSQL;
CREATE EVENT TRIGGER a_ddl_trigger
On 02.06.2015 22:12, Melvin Davidson wrote:
Your problem is in your design.
If you do it like this:
CREATE TABLE A
(
p_col serial PRIMARY KEY,
acol integer
);
CREATE TABLE B() INHERITS (A);
INSERT INTO A(acol) VALUES (1);
INSERT INTO B(acol) VALUES (2);
SELECT * FROM A;
SELECT * FROM B;
Th
On 2015-06-01 14:22:32 -0400, Robert Haas wrote:
> commit d33b4eb0167f465edb00bd6c0e1bcaa67dd69fe9
> Author: Robert Haas
> Date: Fri May 29 14:35:53 2015 -0400
>
> foo
Hehe!
> diff --git a/src/backend/access/transam/multixact.c
> b/src/backend/access/transam/multixact.c
> index 9568ff1.
Your problem is in your design.
If you do it like this:
CREATE TABLE A
(
p_col serial PRIMARY KEY,
acol integer
);
CREATE TABLE B() INHERITS (A);
INSERT INTO A(acol) VALUES (1);
INSERT INTO B(acol) VALUES (2);
SELECT * FROM A;
SELECT * FROM B;
Then the sequence (p_col) will be UNIQUE across
On 02.06.2015 16:20, Melvin Davidson wrote:
You can use the following to list the triggers and see what functions
they call. Then you can check pg_proc to see how TRUNCATE is used in
prosrc.
SELECT c.relname,
t.tgname,
p.pronameAS function_called,
t.tgconstraint
Basically, in an (maybe-over)simplified example:
CREATE OR REPLACE FUNCTION add_transaction(transaction core_transaction)
RETURNS integer AS $$
DECLARE
transaction2 core_transaction;
BEGIN
transaction.field1 := 'lapse’;
transaction2.field2 := transaction.field2;
transaction2.fi
As Tom advised, it's called a "public" schema for a reason. It means the
general public (any user) has access to it and can create objects/tables in
it.
On Tue, Jun 2, 2015 at 2:58 PM, Joshua D. Drake
wrote:
>
> On 06/02/2015 11:46 AM, Tom Lane wrote:
>
>> Adrian Klaver writes:
>>
>>> On 06/02
On 06/02/2015 11:46 AM, Tom Lane wrote:
Adrian Klaver writes:
On 06/02/2015 11:04 AM, Steve Pribyl wrote:
I have noted that "GRANT ALL ON SCHEMA public TO public" is granted
on postgres.schemas.public. I am looking at this in pgadmin so excuse
my nomenclature.
Is this what is allowing wr
This only seems to show up in pgadminIII, I am unable to see this grant using
\dn+(but I am a bit of a novice).
postgres=# \dn+
List of schemas
Name | Owner | Access privileges | Description
+--+--+---
Adrian Klaver writes:
> On 06/02/2015 11:04 AM, Steve Pribyl wrote:
>> I have noted that "GRANT ALL ON SCHEMA public TO public" is granted
>> on postgres.schemas.public. I am looking at this in pgadmin so excuse
>> my nomenclature.
>> Is this what is allowing write access to the database?
> Ye
Thanks for clearing that up.
I seems that any database that gets created has "GRANT ALL ON SCHEMA public TO
public" by default. These are all clean installs.I have found this on
Ubuntu 9.3, The Postgres 9.3 and 9.4 deb packages.
Default postgres from ubuntu, is the version I am testing on.
On 06/02/2015 11:04 AM, Steve Pribyl wrote:
None of the roles have permissions on the postgres database. At this
point they don't have any permissions on any databases.
I have noted that "GRANT ALL ON SCHEMA public TO public" is granted
on postgres.schemas.public. I am looking at this in pga
Yes. It is NEVER a good idea to use GRANT ALL on objects for users. Some
people use that as a short cut for allowing access to schemas and tables,
but in essence, it allows the users to do much more, and that is BAD!
http://www.postgresql.org/docs/9.3/interactive/sql-grant.html
On Tue, Jun 2, 201
On 06/02/2015 11:08 AM, Steve Pribyl wrote:
They all look like this.
CREATE ROLE dbA
NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE NOREPLICATION;
And how are you connecting to the database via psql?
JD
--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Center
On 06/02/2015 11:04 AM, Steve Pribyl wrote:
None of the roles have permissions on the postgres database. At this
point they don't have any permissions on any databases.
I have noted that "GRANT ALL ON SCHEMA public TO public" is granted
on postgres.schemas.public. I am looking at this in pga
They all look like this.
CREATE ROLE dbA
NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE NOREPLICATION;
Steve Pribyl
From: Adrian Klaver
Sent: Tuesday, June 2, 2015 1:06 PM
To: Steve Pribyl; Joshua D. Drake; pgsql-general@postgresql.org
Subject: Re: [GENER
On 06/02/2015 10:50 AM, Steve Pribyl wrote:
Josh,
Via psql:
CREATE ROLE bob LOGIN
NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE NOREPLICATION;
GRANT dbA TO bob;
GRANT dbA_ro TO bob;
GRANT dbB TO bob;
GRANT dbB_ro TO bob;
dbA, dbA_ro, dbB, and dbB_ro are roles.
The burning question would be,
None of the roles have permissions on the postgres database. At this point
they don't have any permissions on any databases.
I have noted that "GRANT ALL ON SCHEMA public TO public" is granted on
postgres.schemas.public. I am looking at this in pgadmin so excuse my
nomenclature.
Is this w
Your problem is probably the "INHERIT" and
GRANT dbA TO bob;
GRANT dbA_ro TO bob;
GRANT dbB TO bob;
GRANT dbB_ro TO bob;
options. If any of the dbA's have the permission to CREATE tables (and I
suspect they do), so will bob.
On Tue, Jun 2, 2015 at 1:50 PM, Steve Pribyl
wrote:
> Josh,
>
> Via p
Here is a follow-up on the step-by-step procedure proposed by PT
#1 - setup postgresql planner's cost estimate settings for my hardware.
--
Current parameters values described in section 18.7.2 haven't been chang
Josh,
Via psql:
CREATE ROLE bob LOGIN
NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE NOREPLICATION;
GRANT dbA TO bob;
GRANT dbA_ro TO bob;
GRANT dbB TO bob;
GRANT dbB_ro TO bob;
dbA, dbA_ro, dbB, and dbB_ro are roles.
I have not created any database yet or assigned permissions to the roles.
Stev
On 2015-06-02 11:49:56 -0400, Robert Haas wrote:
> On Tue, Jun 2, 2015 at 11:44 AM, Andres Freund wrote:
> > On 2015-06-02 11:37:02 -0400, Robert Haas wrote:
> >> The exact circumstances under which we're willing to replace a
> >> relminmxid with a newly-computed one that differs are not altogethe
On 06/02/2015 10:36 AM, Steve Pribyl wrote:
Good Afternoon,
Built a fresh 9.3. postgres server and added some users and noticed that any
user can create tables in any database including the postgres database by
default.
Have I missed some step in securing the default install?
How exactly
Good Afternoon,
Built a fresh 9.3. postgres server and added some users and noticed that any
user can create tables in any database including the postgres database by
default.
Have I missed some step in securing the default install?
Steve Pribyl
[http://www.
On Tue, Jun 02, 2015 at 11:16:22AM -0400, Robert Haas wrote:
> On Tue, Jun 2, 2015 at 1:21 AM, Noah Misch wrote:
> > On Mon, Jun 01, 2015 at 02:06:05PM -0400, Robert Haas wrote:
> > Granted. Would it be better to update both functions at the same time, and
> > perhaps to make that a master-only
On Tue, Jun 2, 2015 at 11:44 AM, Andres Freund wrote:
> On 2015-06-02 11:37:02 -0400, Robert Haas wrote:
>> The exact circumstances under which we're willing to replace a
>> relminmxid with a newly-computed one that differs are not altogether
>> clear to me, but there's an "if" statement protectin
On Tue, Jun 2, 2015 at 11:36 AM, Andres Freund wrote:
>> That would be a departure from the behavior of every existing release
>> that includes this code based on, to my knowledge, zero trouble
>> reports.
>
> On the other hand we're now at about bug #5 attributeable to the odd way
> truncation wo
On 2015-06-02 11:37:02 -0400, Robert Haas wrote:
> The exact circumstances under which we're willing to replace a
> relminmxid with a newly-computed one that differs are not altogether
> clear to me, but there's an "if" statement protecting that logic, so
> there are some circumstances in which we'
Hello Adrian,
May I ask why you need a non-standard model? By standard models I mean the
following:
1) When you don't need to have subclass specific database constraints: All
subclasses in the same table, subclasses that do not have an attribute have
that column null. This has the best performanc
On Tue, Jun 2, 2015 at 11:27 AM, Andres Freund wrote:
> On 2015-06-02 11:16:22 -0400, Robert Haas wrote:
>> I'm having trouble figuring out what to do about this. I mean, the
>> essential principle of this patch is that if we can't count on
>> relminmxid, datminmxid, or the control file to be acc
On 2015-06-02 11:29:24 -0400, Robert Haas wrote:
> On Tue, Jun 2, 2015 at 8:56 AM, Andres Freund wrote:
> > But what *definitely* looks wrong to me is that a TruncateMultiXact() in
> > this scenario now (since a couple weeks ago) does a
> > SimpleLruReadPage_ReadOnly() in the members slru via
> >
On Tue, Jun 2, 2015 at 8:56 AM, Andres Freund wrote:
> But what *definitely* looks wrong to me is that a TruncateMultiXact() in
> this scenario now (since a couple weeks ago) does a
> SimpleLruReadPage_ReadOnly() in the members slru via
> find_multixact_start(). That just won't work acceptably whe
On 2015-06-02 11:16:22 -0400, Robert Haas wrote:
> I'm having trouble figuring out what to do about this. I mean, the
> essential principle of this patch is that if we can't count on
> relminmxid, datminmxid, or the control file to be accurate, we can at
> least look at what is present on the disk
On Tue, Jun 2, 2015 at 1:21 AM, Noah Misch wrote:
> On Mon, Jun 01, 2015 at 02:06:05PM -0400, Robert Haas wrote:
>> On Mon, Jun 1, 2015 at 12:46 AM, Noah Misch wrote:
>> > On Fri, May 29, 2015 at 03:08:11PM -0400, Robert Haas wrote:
>> >> SetMultiXactIdLimit() bracketed certain parts of its
>> >>
So product_feature is only 1 row for each product_type, right ? Looks good.
On Tue, Jun 2, 2015 at 1:15 PM, Adrian Stern
wrote:
> Sorry. Will do in the future.
>
> Product_freature is a table describing the valid keys for product
> features. With this it is possible to limit keys to specific gro
On 06/02/2015 03:10 AM, Filipe Pina wrote:
HI Adrian,
I had a typo in the email:
INSERT INTO my_table VALUES(my_table.*);
was actually
INSERT INTO my_table VALUES(my_var.*);
Aah, that is different:)
So I meant to insert the variable I had in memory (dict representing a row),
not the row
On 06/02/2015 04:16 AM, Mimiko wrote:
Thanks for response.
I've tried to connect the application to postgres with odbc. Arised 2
problems:
1) mysql widelly uses case-insensitive naming for
schemas,tables,columns.
Actually that is not true as I found out the hard way. See here for all
the way
On 06/02/2015 03:59 AM, Tomas Vondra wrote:
On 06/02/15 04:27, Adrian Klaver wrote:
On 06/01/2015 07:11 PM, Arthur Silva wrote:
In my opinion, FWIW, that really does not change anything. Whether
you are dealing with 20 new features over a year or 10 over half a
year the same constraints apply
On 06/02/2015 01:24 AM, Rémi Cura wrote:
Hey,
python is installed from official binary, 64 b for windows,
in C/Python32
I can't remember the argument, but it might be irrelevant.
The problem doesn't seem to be to install numpy, it works perfectly in
the regular terminal.
The problem seems to be
You can use the following to list the triggers and see what functions they
call. Then you can check pg_proc to see how TRUNCATE is used in prosrc.
SELECT c.relname,
t.tgname,
p.pronameAS function_called,
t.tgconstraint AS is_constraint,
CASE WHEN t.tgconstrre
Hello everyone,
I know most of you guys have plenty of experience with PostgreSQL, do any
of you know a tool for windows that allows me to create an automatic
failover system? I'm running Windows servers 2008 and 2012 and PostgreSQL
9.4.
Thanks in advance for your time!
I hate to ask the obvious, but have you made sure you copied over the
postgresql.conf and pg_hba.conf to make it identical?
On Tue, Jun 2, 2015 at 7:39 AM, Bruce Momjian wrote:
> On Tue, Jun 2, 2015 at 04:40:15PM +1200, Fabio Ugo Venchiarutti wrote:
> > We're fairly confident that it's an issue
On June 2, 2015 03:16:53 PM Zenaan Harkness wrote:
> On 6/2/15, Jan de Visser wrote:
> > On June 1, 2015 11:11:37 PM Arthur Silva wrote:
> >> In my opinion a twice a year schedule would be good.
> >> The LTS would be every 2 or 4 releases. Keeping 2 LTS versions supported
> >> at
> >> all moments.
On 2015-06-01 14:22:32 -0400, Robert Haas wrote:
> On Mon, Jun 1, 2015 at 4:58 AM, Andres Freund wrote:
> > The lack of WAL logging actually has caused problems in the 9.3.3 (?)
> > era, where we didn't do any truncation during recovery...
>
> Right, but now we're piggybacking on the checkpoint r
On Tue, Jun 02, 2015 at 12:59:14PM +0200, Tomas Vondra wrote:
> I disagree. The fact that we have 1 release per year means there's one
> deadline, and if you miss it you have to wait another year for the feature
> to be available in official release. That's a lot of pressure and
> frustration for d
On Tue, Jun 02, 2015 at 01:31:55PM +0200, Thomas Kellerer wrote:
> > 2) as program double-quotes the schema,table and column names.
>
> Don't use quoted identifiers. Neither in Postgres nor in MySQL (or any other
> DBMS)
I think a better rule of thumb is either always to use them (and spell
eve
On Tue, Jun 2, 2015 at 04:40:15PM +1200, Fabio Ugo Venchiarutti wrote:
> We're fairly confident that it's an issue with the hardware but we
> have political reasons to downgrade PG to 9.2.10 to show the hosting
> supplier that it's their fault.
>
>
> The release notes for 9.2.11 mention no data
Mimiko schrieb am 02.06.2015 um 13:16:
> 1) mysql widelly uses case-insensitive naming for
> schemas,tables,columns.
So does Postgres. FOO, foo and Foo are all the same name
> But postgres use case-sensitive when doulbe-quoting
Which is what the SQL standard requires (and this was required *lo
Thanks for response.
I've tried to connect the application to postgres with odbc. Arised 2
problems:
1) mysql widelly uses case-insensitive naming for
schemas,tables,columns. But postgres use case-sensitive when
doulbe-quoting or lowers the names without quoting. Is there a configure
option
Sorry. Will do in the future.
Product_freature is a table describing the valid keys for product features.
With this it is possible to limit keys to specific groups of products.
Freundliche Grüsse
Adrian Stern
unchained - web solutions
adrian.st...@unchained.ch
+41 79 292 83 47
On Tue, Jun 2, 2
On 06/02/15 04:27, Adrian Klaver wrote:
On 06/01/2015 07:11 PM, Arthur Silva wrote:
In my opinion, FWIW, that really does not change anything. Whether
you are dealing with 20 new features over a year or 10 over half a
year the same constraints apply, writing the code and getting it
reviewed ov
Please do reply-all so you also reply to the list.
It's not ~good to develop with sqlite and deploy on posgresql. You should
have your 'dev' as close to 'prod' as possible.
Product_feature is another table in this case ?
On Tue, Jun 2, 2015 at 11:44 AM, Adrian Stern
wrote:
> Database changeabi
Thanks Rémi,
Indeed I needed something more generic and easy to maintain (regarding table
schema evolution) so I ended up going back to PL/PGSQL (for that specific
function) in the meantime.
> On 02/06/2015, at 09:41, Rémi Cura wrote:
>
> OUps,
>
> I forget another strategy I used :
> instea
HI Adrian,
I had a typo in the email:
INSERT INTO my_table VALUES(my_table.*);
was actually
INSERT INTO my_table VALUES(my_var.*);
So I meant to insert the variable I had in memory (dict representing a row),
not the rows from the table..
> On 02/06/2015, at 01:44, Adrian Klaver wrote:
>
>
Andreas Ulbrich wrote:
> I'm in a handle for a trigger for TRUNCATE. Is it possible to find out
> whether the TRUNCATE TABLE ist called with CASCADE?
I don't think there is.
But you can find out the table where the trigger is defined and examine
if any foreign key constraints are referring to it.
OUps,
I forget another strategy I used :
instead of having
testp2(es employee[])
you can use
testp2( names text[], salaries integer[], ages integer[])
This might be the solution with the less work, but it is absolutely
terrible practice,
because it will be hard to change you record type (evoluti
Hey,
the only straight workaround I know (which is pretty bad)
is to cast down your record to text.
Then you have an array of text, which is manageable.
For this you can either 'flatten' your record into a unique text,
or cast each part of your record to text, then emulate an array of array
(you n
Hey,
python is installed from official binary, 64 b for windows,
in C/Python32
I can't remember the argument, but it might be irrelevant.
The problem doesn't seem to be to install numpy, it works perfectly in the
regular terminal.
The problem seems to be that postgres can't use correctly numpy.
67 matches
Mail list logo
