set_exist_pos > 0 THEN
> rarity_str := substr($2, colon_pos + 2);
> rarity_exist_str_start := substr($1, 1, set_exist_pos - 1);
> comma_pos :=
> ELSE
>RETURN $1 || \', \' || $2;
> END IF;
> END'
>LANGUAGE 'plpgsql';
>
> ---(end of broadcast)---
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>choose an index scan if your joining column's datatypes do not
>match
--
Chris Kratz
---(end of broadcast)---
TIP 6: explain analyze is your friend
of the records going into the grouping code
since the aggregates we are using are order sensitive. Think functions like
first and last.
-Chris
--
Chris Kratz
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Wednesday 26 April 2006 10:30 am, you wrote:
> Chris Kratz wrote:
> > Hello all,
> >
> > I wanted to verify what we are seeing.
> >
> > Select a, aggregate(b)
> > from c
> > group by a
> > order by a,b
>
> That's a rather odd que
will be processed in the group by with the
specified order? Or will the group by always be arbitrary in it's ordering
of the records?
This is pg 8.1 on Linux.
Thanks,
-chris
--
Chris Kratz
---(end of broadcast)---
TIP 4: Have you searche
On Monday 13 March 2006 03:21 pm, Tom Lane wrote:
> Chris Kratz <[EMAIL PROTECTED]> writes:
> > Thanks for the reply. Yes, subselects would work very well and in some
> > ways are more elegant then the hand waving we had to do to get the
> > multi-column aggregates to
On Thursday 09 March 2006 02:18 pm, Merlin Moncure wrote:
> Chris Kratz wrote:
> > Well for anyone else who may be interested in doing something similar,
> > here is what we did. It does require typecasting going into the
> > functions, composite types and using the dot nota
,8
> 2,32,32,32,32
>
> I think it does what you are trying to do and can be expanded to your
> other examples. Maybe not as cool as using composite aggregates, though.
>
> -- BMT
>
> Chris Kratz wrote:
> >Thanks Tom,
> >
> >Well for anyone else who may b
rpose query tool. Anyway,
thanks for the suggestion.
Thanks,
-Chris
On Thursday 09 March 2006 05:28 pm, Bruno Wolff III wrote:
> On Thu, Mar 09, 2006 at 12:56:21 -0500,
>
> Chris Kratz <[EMAIL PROTECTED]> wrote:
> > Hello All,
> >
> > Is there any way in postgre
:
> Chris Kratz <[EMAIL PROTECTED]> writes:
> > Is there any way in postgres to have an aggregate that uses input from
> > two columns without using composite types?
>
> No.
>
>
and return the
associated data value. Since there may be multiple date columns each with
dependent columns, we can't use a sort by date and a simpler first or last
aggregate.
Thanks,
-Chris
--
Chris Kratz
---(end of broadcast)---
TIP 4:
nk we were anywhere near
wraparound on our live machine, hence we've let it ride.
It sounds like we will need to start thinking about migrating to the
tableoid+rowoid at some point.
Thanks again,
-Chris
On Wednesday 01 February 2006 09:53 am, you wrote:
> Chris Kratz <[EMAIL PROTE
Hello all,
We have a live server running on PG 8.0.3 which we backup on a regular bases
by doing a pg_dumpall --oids. We have a test server currently running 8.1.1
where we reload that dumpall using psql.
Now we have a history tracking system in the db which via triggers and rules
keeps track
CE RULE debug_rule AS
ON INSERT TO test1
do INSERT INTO test_que (row_id)
VALUES (new.id);
insert into test1 (data)
select data from test2;
-- We will have 1 row inserted
select * from test1;
-- But no rows here even though a row was placed in test1
select * from test_que;
rollback
On Monday 21 November 2005 08:16 pm, David Fetter wrote:
> On Mon, Nov 21, 2005 at 08:05:19PM -0500, Jerry Sievers wrote:
> > Chris Kratz <[EMAIL PROTECTED]> writes:
> > > Hello All,
> > >
> > > We have finally tracked down a bug in our application to a
On Monday 21 November 2005 08:05 pm, Jerry Sievers wrote:
> Chris Kratz <[EMAIL PROTECTED]> writes:
> > Hello All,
> >
> > We have finally tracked down a bug in our application to a rewrite rule
> > on a table. In essence, the rewrite rule in question logs any in
Hello All,
We have finally tracked down a bug in our application to a rewrite rule on a
table. In essence, the rewrite rule in question logs any inserts to another
table. This works correctly in all cases except where an "except" clause is
used in the insert statement. In this case, the rows
On Monday 21 November 2005 03:35 pm, you wrote:
> Chris Kratz <[EMAIL PROTECTED]> writes:
> > CREATE OR REPLACE RULE debug_rule AS
> > ON INSERT TO test1
> >do INSERT INTO test_que (row_id)
> > VALUES (new.id);
>
> You would be a whole l
First version of this I sent this morning did not appear to go through.
Please disregard if you received the first one.
-- Original Message --
Hello All,
We have finally tracked down a bug in our application to a rewrite rule on a
table. In essence, the rewrite rule in quest
On Monday 23 May 2005 06:09 pm, Scott Marlowe wrote:
> On Mon, 2005-05-23 at 16:54, Chris Kratz wrote:
> Are you folks running 8.0 with its improved caching algorithms? Just
> wondering if that helps or not.
I should have noted that we are still using 7.4 on our production servers.
separate machine? Or
> > even just making sure that the dump file is being written to a
> > different disk drive than PostgreSQL is running on. All that disk
> > write activity is bound to slow the system down.
> >
> > Matthew
> >
> > From: Martijn van Oosterhout
&
standardize on Dell and by extension Xeon hardware. Do anyone have
recommendations for hosting services that would be able to provide Opteron
based hardware and have decent service? Or are we stuck with Xeons?
--
Chris Kratz
---(end of broadcast
s
We are using postgres 7.4.5 on Linux.
[1] http://jasperreports.sourceforge.net/
[2] http://archives.postgresql.org/pgsql-jdbc/2004-10/msg00280.php
[3] iconv -f iso8859-1 -t utf-8 < dbsnapshot.dumpall > dump-utf-8.dumpall
--
Chris Kratz
---(end o
create database newdb template olddb;
works as well.
-Chris
On Tuesday 01 March 2005 05:08 pm, javier wilson wrote:
> On Tue, 01 Mar 2005 16:30:19 -0500, Michael Romagnoli
>
> <[EMAIL PROTECTED]> wrote:
> > Sorry, I meant to ask about copying databases, not tables (including all
> > data in th
there some other setting that is causing the sort to do strange things.
The only work around we have found is to create a sort column and replace all
spaces with 0 and then sort on that column. Any other suggestions or
workarounds?
Issue was tested on both 7.4.1 and 7.3.4, both running on
24 matches
Mail list logo
