Re: [GENERAL] $foo $bar is BAD

> Although people commonly use $foo $bar in examples, it is actually a misuse > of a VERY rude acronym. > The next time you need to make an example, please try being a little more > original (or meaningful) with your variable names. In light of recent CoC decisions, I would like to propose the

Re: [GENERAL] $foo $bar is BAD

On Friday, April 15, 2016 8:13:56 PM EDT Melvin Davidson wrote: > *Thanks for the sympathetic feedback John. I understand people are > reluctant to change. It was just my intent to enlighten others as to the > true background behind it.* > *So if it's not about to change, then I'll just have to

Re: [GENERAL] $foo $bar is BAD

*Thanks for the sympathetic feedback John. I understand people are reluctant to change. It was just my intent to enlighten others as to the true background behind it.* *So if it's not about to change, then I'll just have to cry $boo $hoo, $oye $vey. :)* On Fri, Apr 15, 2016 at 8:05 PM, John

Re: [GENERAL] $foo $bar is BAD

On Fri, Apr 15, 2016 at 6:35 PM, Melvin Davidson wrote: > > > *Although people commonly use $foo $bar in examples, it is actually a > misuse of a VERY rude acronym.Anyone that has done time in the military, > and other goverment agencies, has been introduced to the term

Re: [GENERAL] $foo $bar is BAD

John R Pierce writes: > On 4/15/2016 4:35 PM, Melvin Davidson wrote: >> *Anyone that has done time in the military, and other goverment >> agencies, has been introduced to the term fubar, which stands for >> "fouled up beyond all repair". Although fouled was replaced by

Re: [GENERAL] $foo $bar is BAD

On 4/15/2016 4:35 PM, Melvin Davidson wrote: *Anyone that has done time in the military, and other goverment agencies, has been introduced to the term fubar, which stands for "fouled up beyond all repair". Although fouled was replaced by another similar word where the 2nd, 3rd and 4th letters

[GENERAL] $foo $bar is BAD

*Although people commonly use $foo $bar in examples, it is actually a misuse of a VERY rude acronym.Anyone that has done time in the military, and other goverment agencies, has been introduced to the term fubar, which stands for "fouled up beyond all repair". Although fouled was replaced by

Re: [GENERAL] pg_basebackup: return value 1: reason?

Andrej Vanek writes: > Hello,  > > I tried to run pg_basebackup. Return value is 1. > > How to find out its reason? > (I suspect that some wal after backup is missing- but how to find out the > real reason? How to fix it?) Well there are more than 80 cases of exit

Re: [GENERAL] pg_basebackup: return value 1: reason?

On 04/15/2016 03:28 PM, Andrej Vanek wrote: Hello, I tried to run pg_basebackup. Return value is 1. How to find out its reason? (I suspect that some wal after backup is missing- but how to find out the real reason? How to fix it?) First it is not clear to me where you are taking the backup

[GENERAL] pg_basebackup: return value 1: reason?

Hello, I tried to run pg_basebackup. Return value is 1. How to find out its reason? (I suspect that some wal after backup is missing- but how to find out the real reason? How to fix it?) thanks, Andrej --details: environment: CentOS 6.7, postgres 9.5.1 ( PostgreSQL 9.5.1 on

Re: [GENERAL] Deadlock between VACUUM and ALTER TABLE commands

On 14/04/16 18:34, Kevin Burke wrote: Unfortunately *I'm still seeing a very slow query which is affecting our tests. *It's happening with roughly the same frequency as the previous error. * * The query log is here: https://gist.github.com/kevinburkeshyp/f1a4f73f8933e027aebbc53283acced2** *

Re: [GENERAL] Question about ranking & full text

On 15.04.2016 15:47, Nicolas Paris wrote: Hi, I wonder why the third query returns 0. To me, it would return 0.1, because there is not baz in the text Thanks ! (pg 9.4) SELECT ts_rank_cd(apod.t, query,4) AS rank FROM (SELECT to_tsvector('foo baz') as t) as apod, to_tsquery('foo & baz') query

[GENERAL] Question about ranking & full text

Hi, I wonder why the third query returns 0. To me, it would return 0.1, because there is not baz in the text Thanks ! (pg 9.4) SELECT ts_rank_cd(apod.t, query,4) AS rank FROM (SELECT to_tsvector('foo baz') as t) as apod, to_tsquery('foo & baz') query WHERE query @@ apod.t; rank|

Re: [GENERAL] Deadlock between VACUUM and ALTER TABLE commands

On 14/04/16 18:34, Kevin Burke wrote: Unfortunately *I'm still seeing a very slow query which is affecting our tests. *It's happening with roughly the same frequency as the previous error. * * The query log is here: https://gist.github.com/kevinburkeshyp/f1a4f73f8933e027aebbc53283acced2** *