Hello,
I have written a update & delete trigger of a table.
My delete trigger runs an update statement but this create a (semantic) problem.
How can I disable the update trigger for only this update call within the
delete trigger?
So my delete trigger need not call the update trigger
Thanks
Phi
Hi,
OK, first, I know the reason of this error "index row size 3040 exceeds btree
maximum, 2712" and know that we cannot create index on certain columns with
size larger than 1/3 buffer page size.
The question is, no matter if I deleted records that caused the problem or all
records of the tab
Hi,
On 13.10.2013 17:43, akp geek wrote:
> Sorry all not posting clear. I posted our postresql.conf file. What
> we are having is very slow response from the database.
>
> would like to get some feedback about postgresql.conf file
> parameters that I posted are causing the issue for performance
thanks for the advice..
Regards
On Sun, Oct 13, 2013 at 6:10 PM, Sergey Konoplev wrote:
> On Sun, Oct 13, 2013 at 2:40 PM, akp geek wrote:
> > thank you all. We will upgrade to 64bit postgres 9.2.5 and take all your
> > suggestions for that. Mean while will run the pg_reorg or pg_repack to
On Sun, Oct 13, 2013 at 2:40 PM, akp geek wrote:
> thank you all. We will upgrade to 64bit postgres 9.2.5 and take all your
> suggestions for that. Mean while will run the pg_reorg or pg_repack to take
> the bloat of the DB. Also pg_repack not installing on the solaris . I will
> try pg_reorg.
W
thank you all. We will upgrade to 64bit postgres 9.2.5 and take all your
suggestions for that. Mean while will run the pg_reorg or pg_repack to
take the bloat of the DB. Also pg_repack not installing on the solaris . I
will try pg_reorg.
Regards
On Sun, Oct 13, 2013 at 4:58 PM, John R Pierce w
On 10/13/2013 1:45 PM, Sergey Konoplev wrote:
On Sun, Oct 13, 2013 at 8:35 AM, akp geek wrote:
>thanks for the advice. One question I have is if I increase the
>shared_buffers to 16GB, then it won't restart because for the 32 bit version
>of postgres , we can't have shared buffers more than 3.2
On Sun, Oct 13, 2013 at 8:35 AM, akp geek wrote:
> thanks for the advice. One question I have is if I increase the
> shared_buffers to 16GB, then it won't restart because for the 32 bit version
> of postgres , we can't have shared buffers more than 3.2 GB right ? ( this
> from various blogs that I
On 10/13/2013 8:35 AM, akp geek wrote:
thanks for the advice. One question I have is if I increase the
shared_buffers to 16GB, then it won't restart because for the 32 bit
version of postgres , we can't have shared buffers more than 3.2 GB
right ? ( this from various blogs that I have read )
On Sun, Oct 13, 2013 at 8:43 AM, akp geek wrote:
> Sorry all not posting clear. I posted our postresql.conf file. What we
> are having is very slow response from the database.
>
> would like to get some feedback about postgresql.conf file parameters that
> I posted are causing the issue for perf
Sorry all not posting clear. I posted our postresql.conf file. What we are
having is very slow response from the database.
would like to get some feedback about postgresql.conf file parameters that
I posted are causing the issue for performance of the DB.
Our database is about 60GB and performan
thanks for the advice. One question I have is if I increase the
shared_buffers to 16GB, then it won't restart because for the 32 bit
version of postgres , we can't have shared buffers more than 3.2 GB right ?
( this from various blogs that I have read )
Thanks again for helping me out
On Fri, Oc
12 matches
Mail list logo
