On Wednesday, April 16, 2014, Jeff Janes wrote:
> On Tue, Apr 15, 2014 at 6:36 PM, Nick Eubank
>
> > wrote:
>
>> Hi all,
>>
>> A few years ago someone said postgres windows can't set working_mem above
>> about 2 GB (www.postgresql.org/message-id/17895.1315869...@sss.pgh.pa.us--
>> seems to be
On Tue, Apr 15, 2014 at 6:36 PM, Nick Eubank wrote:
> Hi all,
>
> A few years ago someone said postgres windows can't set working_mem above
> about 2 GB (www.postgresql.org/message-id/17895.1315869...@sss.pgh.pa.us--
> seems to be same for maintenance_working_mem ). Im finding limit still
> pres
> On 16 Apr 2014, at 17:35, "Nick Eubank" wrote:
>
>
>
>
>> On Wed, Apr 16, 2014 at 1:29 AM, amulsul wrote:
>> >Anyone found a work around?
>>
>> Wouldn't it helpful, setting it in your session?
>>
>> set work_mem='2000MB';
>> set maintenance_work_mem='2000MB';
>>
>> do rest of sql after
On Wed, Apr 16, 2014 at 1:29 AM, amulsul wrote:
> >Anyone found a work around?
>
> Wouldn't it helpful, setting it in your session?
>
> set work_mem='2000MB';
> set maintenance_work_mem='2000MB';
>
> do rest of sql after .
>
> Regards,
> Amul Sul
>
>
>
> --
> View this message in context:
> h
On 16/04/14 17:57, Heikki Linnakangas wrote:
> On 04/16/2014 06:13 PM, Linos wrote:
>> I thought that Postgresql would optimize out joins on columns I
>> don't ask for when I use the view but it doesn't, this query:
>
> It doesn't, because it would be wrong. It still has to check that the tables
On 04/16/2014 06:13 PM, Linos wrote:
I thought that Postgresql would optimize out joins on columns I
don't ask for when I use the view but it doesn't, this query:
It doesn't, because it would be wrong. It still has to check that the
tables have a matching row (or multiple matching rows).
If
Hello all,
I am trying to simplify some of the queries I use with my database creating a
big view of all the possible attributes my items can have, the view is rather
large:
http://pastebin.com/ScnJ8Hd3
I thought that Postgresql would optimize out joins on columns I don't ask for
when I use
Following are the tables
---
CREATE TABLE equipment (
contract_nr varchar(32) COLLATE "C" NULL DEFAULT NULL,
name varchar(64) COLLATE "C"
>Anyone found a work around?
Wouldn't it helpful, setting it in your session?
set work_mem='2000MB';
set maintenance_work_mem='2000MB';
do rest of sql after .
Regards,
Amul Sul
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Workaround-for-working-mem-max-value
