Re: [GENERAL] Include.d and warnings

But max_connections did not change before the reload. It is just overruled in an included configuration file. This is fixed in 9.4 and up. Since it's just cosmetic, we did not back-patch the change. We're running 9.4.4. I've just tested this, and doing a "restart" followed by a "reload" cau

[GENERAL] When files in pg_multixact/{members,offsets} get recycled?

Hello, Running latest 9.3.9. Database was never pg_upgraded. I list pg_multixact/offsets and pg_multixact/members and I see many files with dates more than one year old. Is that ok? # ls -1 members/[0-9A-F]* | wc -l 894 # ls -la members | head total 127064 drwx-- 2 pgsql pgsql 896

Re: [GENERAL] When files in pg_multixact/{members,offsets} get recycled?

Piotr Gasidło wrote: > Running latest 9.3.9. Database was never pg_upgraded. I list > pg_multixact/offsets and pg_multixact/members and I see many files > with dates more than one year old. Is that ok? Yes, it's okay, if a bit annoying. You can decrease the number of files by reducing the freeze

[GENERAL] Correct place for feature requests

Good day. Is there any correct place for feature requests? Thanks. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Correct place for feature requests

Try thhis: https://postgresql.uservoice.com/forums/21853-general On Thu, Jun 25, 2015 at 1:03 PM, Алексей Бережняк wrote: > Good day. > > Is there any correct place for feature requests? > > Thanks. > > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make change

Re: [GENERAL] Correct place for feature requests

I think that PostgreSQL is great RDBMS, but one important (for me) feature that it missing is case-insensitive identifier quotes ([table].[column]) like in Microsoft SQL Server. I know that there are double quotes, but they are case-sensitive. Or maybe some option that will make double quotes cas

Re: [GENERAL] Correct place for feature requests

=?UTF-8?B?0JDQu9C10LrRgdC10Lkg0JHQtdGA0LXQttC90Y/Qug==?= writes: > Is there any correct place for feature requests? Starting a thread here is a reasonable way. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to y

Re: [GENERAL] Correct place for feature requests

On 6/25/2015 11:59 AM, Алексей Бережняк wrote: I think that PostgreSQL is great RDBMS, but one important (for me) feature that it missing is case-insensitive identifier quotes ([table].[column]) like in Microsoft SQL Server. putting names in [ ] is not part of any SQL specification. I know t

Re: [GENERAL] Correct place for feature requests

John R Pierce wrote: > On 6/25/2015 11:59 AM, Алексей Бережняк wrote: > >Or maybe some option that will make double quotes case-insensitive. > > the current behavior is compliant with the SQL specification. if you want > case-insensitive, don't quote the identifiers. if you do quote them, the

Re: [GENERAL] Correct place for feature requests

On Thu, Jun 25, 2015 at 3:29 PM, John R Pierce wrote: > On 6/25/2015 11:59 AM, Алексей Бережняк wrote: > >> I think that PostgreSQL is great RDBMS, but one important (for me) >> feature that it missing is case-insensitive identifier quotes >> ([table].[column]) like in Microsoft SQL Server. >> >

Re: [GENERAL] Correct place for feature requests

I understand that, but it seem there are no way to use words like "group", or "case" without enclosing them into double quotes (and therefore making them case-sensitive). 2015-06-25 22:29 GMT+03:00 John R Pierce : > On 6/25/2015 11:59 AM, Алексей Бережняк wrote: >> >> I think that PostgreSQL is gr

Re: [GENERAL] Correct place for feature requests

On 6/25/2015 12:33 PM, Alvaro Herrera wrote: What happens if you have spaces in your identifiers? either don't do that, or use quoted identifiers and be consistent about your case. what if you have spaces in your identifiers in your java/c/python/perl/php/basic/fortran/etc program? oh wai

Re: [GENERAL] BDR: Can a node live alone after being detached

> >> You shouldn't part a node from its self. The next revision will > >> prevent this with an error. > > > > > > Ok, this was not clear for me. > > Or anyone else, hence the coming docs and code changes. > > Sorry to bother again about that, but what about the "detached node cleanup" best practice

Re: [GENERAL] Correct place for feature requests

On 06/25/2015 12:52 PM, Алексей Бережняк wrote: I understand that, but it seem there are no way to use words like "group", or "case" without enclosing them into double quotes (and therefore making them case-sensitive). From here: https://technet.microsoft.com/en-us/library/ms176027%28v=sql.105

[GENERAL] Re: INSERT a real number in a column based on other columns OLD INSERTs

Thanks to everybody I already solved, the correct syntax was... SELECT t.time_index FROM table_ebscb_spa_log04 t WHERE t.fn_name = NEW.fn_name AND (t.time_type = 'Start' OR time_type = 'Lap') ORDER BY t.stmtserial DESC LIMIT 1 INTO t_ix; Thanks for all again. -- View this message in context: h

[GENERAL] Get the difference between two timestamp cells but in a special format in PostgreSQL

This is my table... I would like to get the time difference between 'time_type = Lap' AND 'time_type = Start' in order to fill 'time_elapse'. Im almost sure that this code works... *CREATE OR REPLACE FUNCTION timediff() RETUR

Re: [GENERAL] Get the difference between two timestamp cells but in a special format in PostgreSQL

You may be looking for to_char: # select to_char( now() - '2015-06-25', '-MM-DD HH24:mm:ss' ); to_char - -00-00 15:00:43 (1 row) http://www.postgresql.org/docs/9.4/static/functions-formatting.html On Wed, Jun 24, 2015 at 9:11 PM, litu16 wrote: > This is my

Re: [GENERAL] Get the difference between two timestamp cells but in a special format in PostgreSQL

(But don't use my format string, it's very wrong!) On Thu, Jun 25, 2015 at 3:20 PM, Colin Lieberman wrote: > You may be looking for to_char: > > # select to_char( now() - '2015-06-25', '-MM-DD HH24:mm:ss' ); > >to_char > - > -00-00 15:00:43 > (1 row) > > http

Re: [GENERAL] Get the difference between two timestamp cells but in a special format in PostgreSQL

On 06/24/2015 09:11 PM, litu16 wrote: This is my table... I would like to get the time difference between 'time_type = Lap' AND 'time_type = Start' in order to fill 'time_elapse'. Im almost sure that this code works... *CREATE OR

Re: [GENERAL] Re: INSERT a real number in a column based on other columns OLD INSERTs

On 25/06/15 16:06, litu16 wrote: SELECT t.time_index FROM table_ebscb_spa_log04 t WHERE t.fn_name = NEW.fn_name AND (t.time_type = 'Start' OR time_type = 'Lap') ORDER BY t.stmtserial DESC LIMIT 1 INTO t_ix; Please format your SQL, as it makes it easier to read! But, you don't have to follow my c

Re: [GENERAL] Inserting from multiple processes?

On Tue, Jun 9, 2015 at 8:38 AM, Dave Johansen wrote: > On Mon, Jun 8, 2015 at 10:15 AM, Dave Johansen > For the sake of documentation, here's the function that I used to > accomplish this: > CREATE FUNCTION insert_test_no_dup(tutc_ TIMESTAMP WITHOUT TIME ZONE, id_ > INTEGER, value_ INTEGER) RETU

[GENERAL] Question about the isolation level and visible

Hi, all, I start two session with the following execute time order: session1: START TRANSACTION ISOLATION LEVEL SERIALIZABLE; session2: INSERT INTO t1 values(1); session2: COMMIT; session1: SELECT * FROM t1; I found session1 got the value 1 which is inserted by session2. Is there any way to

Re: [GENERAL] BDR: Can a node live alone after being detached

On 26 June 2015 at 04:59, Sylvain MARECHAL wrote: > >> >> You shouldn't part a node from its self. The next revision will >> >> prevent this with an error. >> > >> > >> > Ok, this was not clear for me. >> >> Or anyone else, hence the coming docs and code changes. >> > Sorry to bother again about t

Re: [GENERAL] Question about the isolation level and visible

From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of 娄帅 Sent: Friday, June 26, 2015 9:12 AM To: pgsql-general@postgresql.org Subject: [GENERAL] Question about the isolation level and visible Hi, all, I start two session with the following execute time

Re: [GENERAL] BDR: Can a node live alone after being detached

Le 26/06/2015 03:26, Craig Ringer a écrit : [...] Sorry to bother again about that, but what about the "detached node cleanup" best practice? Suppose I have 2 nodes, 'node1' and 'node2'. So I am OK to call bdr_part_by_node_names('node2') on node1 to detach node2. But then, is it safe to call bd