Re: [DOCS] 36.2 Visibility of Data Changes

2016-04-29 Thread Peter Eisentraut
On 08/11/2015 06:18 AM, Dmitry Igrishin wrote: > Subparagraph 1: > I suggest to replace > "Statement-level triggers follow simple visibility rules: none of the > changes made by a statement are visible to statement-level > triggers that are invoked before the statement, whereas all > modifications

Re: [DOCS] 36.1 Overview of Trigger Behavior

2016-04-29 Thread Peter Eisentraut
On 08/11/2015 05:51 AM, Dmitry Igrishin wrote: > Subparagraph 8: > I suggest to replace > "BEFORE row-level triggers to execute" > with > "row-level BEFORE triggers to execute" > for consistency. Fixed that one. Wasn't so sure about the one below. > > Subparagraph 14: > While WHEN can be used w

Re: [DOCS] COPY options

2016-04-29 Thread Andrei M. Eichler
Thanks for the replies, I'm using postgres since 8.3 and didn't notice at the time of 9.0 release the change in the syntax, as the old syntax still works, every time I read the current documentation I didn't notice that I was using it wrong. I agree with Tom Lane about leaving it alone. Another q

Re: [DOCS] Date formatting

2016-04-29 Thread Andrei M. Eichler
I don't understand exactly what are your problem. In the beginning of your email, you said that you want to convert a text to timestamp, which can be done like this: select 'Tue Sep 24 08:56:18 + 2013'::timestamp -- 2013-09-24 08:56:18 What you refer as "meaningless parts" are day of week an

Re: [DOCS] COPY options

2016-04-29 Thread Tom Lane
Kevin Grittner writes: > It's not really a question of whether we should go back to > documenting the deprecated syntax, but whether (and when) support > for it should finally be ripped out. It was last documented in 8.4. We still document, and support, not only the pre-9.0 COPY syntax but also

Re: [DOCS] COPY options

2016-04-29 Thread Kevin Grittner
On Fri, Apr 29, 2016 at 10:31 AM, Andrei M. Eichler wrote: > Following the documentation, I wrote this COPY FROM command: > > COPY test_copy FROM '/mnt/disk1/files/test_file.csv' with csv header > delimiter ';' force_null date_column, date_column2, date_column3, > date_column4, date_column5 encod

Re: [DOCS] COPY options

2016-04-29 Thread Tom Lane
"Andrei M. Eichler" writes: > Following the documentation, I wrote this COPY FROM command: > COPY test_copy FROM '/mnt/disk1/files/test_file.csv' with csv header > delimiter ';' force_null date_column, date_column2, date_column3, > date_column4, date_column5 encoding 'latin1'; Which part of the

Re: [DOCS] COPY options

2016-04-29 Thread Andrei M. Eichler
Hi, thanks for the wiki link. I'm using Postgrees 9.5.2, running on Debian 8.4 I have a csv file with all columns quoted, even null values. Following the documentation, I wrote this COPY FROM command: COPY test_copy FROM '/mnt/disk1/files/test_file.csv' with csv header delimiter ';' force_null

[DOCS] Date formatting

2016-04-29 Thread Mavka
To convert a string to date I need to omit meaningless parts. I found this format working well (Twitter dump format): SELECT to_timestamp( 'Tue Sep 24 08:56:18 + 2013', 'xxx Mon DD HH24:MI:SS x ' ) -- 2013-09-24 08:56:18-07 In place of "xxx" I can use any non-reserved symbols, e.g