2010/1/21 Vincenzo Romano :
> And, BTW:
> EXECUTE 'INSERT INTO '||partition-table-name||' SELECT $1.*' USING NEW;
won't work on 8.3 where I need it however :)
--
GJ
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgre
2010/1/21 Grzegorz Jaśkiewicz :
> http://www.pubbs.net/pgsql/201001/16503/
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
Grzegorz,
Thanks for the reference, which officially i
http://www.pubbs.net/pgsql/201001/16503/
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
W dniu 20 stycznia 2010 12:01 użytkownik Grzegorz Jaśkiewicz <
gryz...@gmail.com> napisał:
> please use search before asking.
>
please use search before advising to use search; it's not so easy to find.
can you share a link to archived post?
Filip
2010/1/20 Vincenzo Romano :
> 2010/1/20 Adrian von Bidder :
>> Hi,
>>
>> On Wednesday 20 January 2010 11.57:37 Vincenzo Romano wrote:
>>> 2010/1/20 Adrian von Bidder :
>>
>>> > [ creating db partitions on demand ]
>>> >
>>> > On Wednesday 20 January 2010 11.20:21 Vincenzo Romano wrote:
>>> >> In ca
2010/1/20 Adrian von Bidder :
> Hi,
>
> On Wednesday 20 January 2010 11.57:37 Vincenzo Romano wrote:
>> 2010/1/20 Adrian von Bidder :
>
>> > [ creating db partitions on demand ]
>> >
>> > On Wednesday 20 January 2010 11.20:21 Vincenzo Romano wrote:
>> >> In case 1 I need to inspect the catalog with
Hi,
On Wednesday 20 January 2010 11.57:37 Vincenzo Romano wrote:
> 2010/1/20 Adrian von Bidder :
> > [ creating db partitions on demand ]
> >
> > On Wednesday 20 January 2010 11.20:21 Vincenzo Romano wrote:
> >> In case 1 I need to inspect the catalog with at least a select, while
> >> in case 2
I submitted a solution here once in the past, please use search before asking.
the exception handling will be quicker in general, cos you won't have
to test for existence of the table before every insert.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to you
2010/1/20 Adrian von Bidder :
> Hi,
>
> [ creating db partitions on demand ]
>
> On Wednesday 20 January 2010 11.20:21 Vincenzo Romano wrote:
>> In case 1 I need to inspect the catalog with at least a select, while
>> in case 2 I need to trap errors.
>> In my (little) experience trapping errors is
Hi,
[ creating db partitions on demand ]
On Wednesday 20 January 2010 11.20:21 Vincenzo Romano wrote:
> In case 1 I need to inspect the catalog with at least a select, while
> in case 2 I need to trap errors.
> In my (little) experience trapping errors is slow, so I would go for
> option 1.
Tra
A main issue in my case with the suggested (chapter 5.9)
implementation is that child tables need to be created in advance,
For a number of reasons (complex partitioning schemas, rows also
related to the past and the future) it'd be unpractical
to create all of them in advance.
So I'm thinking abou
Hello all,
still with partitioning...
wheter I use rules or triggers is there a way for me _not_ to specify
field-by-field all the fields I wish to be redirected to the
child-table...
as example:
instead of this:
-
create rule insert_t_1
8><
> For some more info, I've given at least one presentation on the topic, which
> seems to be missing from the omniti site, but I've uploaded it to
> slideshare...
> http://www.slideshare.net/xzilla/postgresql-partitioning-pgcon-2007-presentation
>
> HTH.
>
8><
Very nice presentation. I have 2
On Thursday 11 September 2008 07:47:00 Joao Ferreira gmail wrote:
> Hello all,
>
> my application is coming to a point on which 'partitioning' seems to be
> the solution for many problems:
>
> - query speed up
> - data elimination speed up
>
> I'dd like to get the feeling of it by talking to people
Hello all,
my application is coming to a point on which 'partitioning' seems to be
the solution for many problems:
- query speed up
- data elimination speed up
I'dd like to get the feeling of it by talking to people who use
partitioning, in general..
- good, bad,
- hard to manage, easy to man
hi chris
as u know i'm a chinese and a freshman to postgres so forgive my poor
english.
child table "news_001" dose inherit the table "news".
for that reason it gets all fields which the master has,and i changed
nothing on it.
when i executed a query like
"INSERT INTO news(title,content,author)
On 4/1/06, fufay <[EMAIL PROTECTED]> wrote:
> dear all,
> i created a master table and a sub table which inherits the main table.
> and then i made a trigger and a function that want to keep the master table
> empty.
> but the trigger didn't work anyway.when i inserted data into the table
> "news",
dear all,
i created a master table and a sub table which inherits the main table.
and then i made a trigger and a function that want to keep the master table
empty.
but the trigger didn't work anyway.when i inserted data into the table
"news",both the master table
and the sub table were inserted.
18 matches
Mail list logo
