On Thu, Jan 3, 2013 at 8:44 AM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 7781
> Logged by: Alexander Shniperson
> Email address: alex.shniper...@gmail.com
> PostgreSQL version: 9.1.7
> Operating system: osx lion 10.7.5
> Description:
>
> H
The following bug has been logged on the website:
Bug reference: 7785
Logged by: Dag Lem
Email address: d...@nimrod.no
PostgreSQL version: 9.2.1
Operating system: RedHat EL 5.8
Description:
Hi,
The test case below demonstrates that the planner pushes down the WHERE (
The following bug has been logged on the website:
Bug reference: 7786
Logged by: Douglas Toltzman
Email address: d...@oakstreetsoftware.com
PostgreSQL version: 9.2.2
Operating system: Linux CentOS
Description:
in the interest of simplicity, I've got a view that calls
On Fri, Jan 4, 2013 at 3:15 PM, Aleksander Shniperson
wrote:
> I can't do that, every time i run ApplicationBuilder i see new version 3.3.0,
> then i chose "next next next" and nothing changes.
>
Define "nothing changes" please. Do you mean it doesn't fix the
problem? It works fine for me here:
On Fri, Jan 4, 2013 at 3:43 PM, Aleksander Shniperson
wrote:
> Sorry.
>
> It does not fix the problem.
>
>> /Library/pgAgent
> path not exists.
So where did you install it if that path doesn't exist? My suggestion
would be to figure that out, then uninstall the old version before
starting over wi
"e.g." means "for example". Once you've figured out where it is
installed, you should substitute the correct path into the example I
gave.
On Fri, Jan 4, 2013 at 4:28 PM, Aleksander Shniperson
wrote:
> LoL
>
> path /Library/pgAgent does not exists, i can't run uninstall
>
> 04.01.2013, в 20:18, D
On Fri, Jan 4, 2013 at 4:35 PM, Aleksander Shniperson
wrote:
> sudo find / -name "uninstall-pgagent.app"
>
> gives no result.
What's in /etc/postgres-reg.ini?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL
d...@nimrod.no writes:
> The test case below demonstrates that the planner pushes down the WHERE (ON)
> clause in a UNION ALL view, but fails to push down the WHERE (ON) clause
> when a JOIN clause is introduced in the view.
> Any simple fix? :-)
No.
(See is_safe_append_member() for why not.)
d...@oakstreetsoftware.com writes:
> in the interest of simplicity, I've got a view that calls a stored procedure
> to compute a value ...
> create view testv as select tt.field1, tt.intfield, compute_val(tt.field1)
> AS compute1 from tt;
> If compute_val() selects sum(intfield) from the testv vi
