On Fri, Sep 23, 2011 at 3:03 AM, Mike Christensen wrote:
> 1) Though I might have given the impression that a “manual complete
> refresh” is not useful, I definitely see value in this especially for
> data warehousing scenarios. However, I’d almost want to call this a
> “snapshot” and not a “mate
On Wed, Sep 21, 2011 at 11:34 PM, Craig Ringer wrote:
[snip]
> This can get complicated when you have triggers acting recursively on a
> table and it isn't always that easy to understand exactly what a trigger
> will see.
I do agree with most all your points. The value I got out of this
experien
On 09/22/2011 01:34 AM, Mike Christensen wrote:
If Oracle was a swimming pool, I would have those little floaty duck
things on my arms.
Yes, it's too bad the license to get Oracle 11g with Floaties is cost
prohibitive for most companies.
--
Greg Smith 2ndQuadrant USg...@2ndquadrant.com
On 09/21/2011 11:34 PM, Mike Christensen wrote:
[ much omitted ]
> One of the major components I'm working on is this reporting engine
> that runs these major huge expensive queries (seriously, some of them
> take 2-3 minutes to run) to generate data that gets dumped to an Excel
> file for VPs t
Hello,
..
> up front, I'm not a database expert by any means and I'm nowhere close
> to an Oracle expert, or even an Oracle novice. If Oracle was a
> swimming pool, I would have those little floaty duck things on my
> arms.
Please go through this link
http://asktom.oracle.com/pls/asktom/f?p=100:1
Craig Ringer, 22.09.2011 08:34:
- You don't see materialized views without selective updating ("fast
refresh") as useful. [I disagree, though I can see how it wouldn't be
very useful for the particular use case you're facing.]
One thing that is often overlooked and that I find most useful is th
On 09/22/2011 01:34 PM, Mike Christensen wrote:
[lots]
I'm going to heavily paraphrase a summary, then a summarized response.
If you disagree with the way I interpret and condense the full message,
please feel free to grump. Roughly, I read your comments as:
- You're focused on a single use-
>> Hmm I think a materialized view you have to update yourself is called a
>> "table".. but after dealing with the nightmare that is Oracle 11g, I
>> think it'd be much more fun going that route with triggers and
>> everything. Yes this thread is a complete vent, and also a plea to the
>> pg guys
On 09/22/2011 06:02 AM, Mike Christensen wrote:
Hmm I think a materialized view you have to update yourself is called a
"table".. but after dealing with the nightmare that is Oracle 11g, I
think it'd be much more fun going that route with triggers and
everything. Yes this thread is a complete v
On Wed, Sep 21, 2011 at 2:54 PM, Ben Chobot wrote:
> On Sep 21, 2011, at 1:17 PM, Mike Christensen wrote:
>
> So I used to think materialized views in Postgres would be an awesome
> feature. That is until I had to endure the hell hole which is Oracle's
> implementation.. what a complete joke..
Hmm I think a materialized view you have to update yourself is called a
"table".. but after dealing with the nightmare that is Oracle 11g, I think
it'd be much more fun going that route with triggers and everything. Yes
this thread is a complete vent, and also a plea to the pg guys to do
material
On Sep 21, 2011, at 1:17 PM, Mike Christensen wrote:
> So I used to think materialized views in Postgres would be an awesome
> feature. That is until I had to endure the hell hole which is Oracle's
> implementation.. what a complete joke.. did MS SQL's indexed views do any
> better? Hopeful
So I used to think materialized views in Postgres would be an awesome
feature. That is until I had to endure the hell hole which is Oracle's
implementation.. what a complete joke.. did MS SQL's indexed views do any
better? Hopefully if PG 10 implements this, they'll make it actually useful
to p
13 matches
Mail list logo
