Hi all
Something it's tricky for me here, see my trigger I wrote below. What can I
do to insert c_code from center table INTO center_changed table with ONLY
the c_code where the update was made or where an INSERT of the new entry
INTO center table what made .
Let's say the center table has got
Please help
-Original Message-
From: Khangelani Gama [mailto:kg...@argility.com]
Sent: Thursday, May 22, 2014 9:38 AM
To: 'Adrian Klaver'; 'pgsql-general@postgresql.org'
Subject: RE: [GENERAL] Need help on triggers - postgres 9.1.2
Hi all
Something it's tricky for me here, see my trigger
Hi
My problem is on two lines, INSERT statements, I get an error saying c_cde
does not exist
INSERT INTO center_changed SELECT c_cde, now(); - My problem is here: I
get an error saying c_cde does not exist, I cant how I can give
center_change table the results. Center table has got many rows so
On 22/05/2014 13:48, Khangelani Gama wrote:
> Hi
>
> My problem is on two lines, INSERT statements, I get an error saying c_cde
> does not exist
>
> INSERT INTO center_changed SELECT c_cde, now(); - My problem is here: I
> get an error saying c_cde does not exist, I cant how I can give
You nee
Thanks , I will try that
-Original Message-
From: Raymond O'Donnell [mailto:r...@iol.ie]
Sent: Thursday, May 22, 2014 2:54 PM
To: Khangelani Gama; Andrew Sullivan; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Need help on triggers - postgres 9.1.2
On 22/05/2014 13:48, Khangelani
> > -Original Message-
> > From: Khangelani Gama [mailto:kg...@argility.com]
> > Sent: Thursday, May 22, 2014 9:38 AM
> > To: 'Adrian Klaver'; 'pgsql-general@postgresql.org'
> > Subject: RE: [GENERAL] Need help on triggers - postgres 9.1.2
> >
> > Hi all
> >
> > Something it's tricky for me
On Thu, May 22, 2014 at 02:48:48PM +0200, Khangelani Gama wrote:
> > CREATE OR REPLACE FUNCTION check_center_changes() RETURNS TRIGGER AS
> > $center_changed$
> >
> > BEGIN
> >
> > IF (TG_OP = 'UPDATE') THEN
> > INSERT INTO center_changed SELECT c_cde, now();
PostgreSQL probab
Many Thanks, I will try it now
-Original Message-
From: Igor Neyman [mailto:iney...@perceptron.com]
Sent: Thursday, May 22, 2014 2:55 PM
To: Khangelani Gama; Andrew Sullivan; pgsql-general@postgresql.org
Subject: RE: [GENERAL] Need help on triggers - postgres 9.1.2
> > -Original Messa
On Wed, May 21, 2014 at 7:50 PM, David G Johnston <
david.g.johns...@gmail.com> wrote:
> Laurentius Purba wrote
> > Hello all,
> >
> > I've been seeing lots of this processes in my database DEALLOCATE
> > pdo_stmt_0001 with idle state.
> >
> > Executing *select * from pg_stat_activity where qu
On 05/22/2014 06:01 AM, Khangelani Gama wrote:
Many Thanks, I will try it now
In the link I sent previously:
http://www.postgresql.org/docs/9.3/interactive/plpgsql-trigger.html
there is a handy section (40.9.1. Triggers on data changes) that
explains what information is available to a plpgs
>
>
>> 9.3 - On an idle connection the value of query is the last executed query
>> -
>> which in this case is some form session cleanup command before returning
>> the
>> connection to the pool.
>>
>>
> So, it is a normal behavior in Postgres.
>
> One more thing that bothers me, why this idle con
Thank you very much to everyone, it worked
-Original Message-
From: Khangelani Gama [mailto:kg...@argility.com]
Sent: Thursday, May 22, 2014 3:01 PM
To: 'Igor Neyman'; 'Andrew Sullivan'; 'pgsql-general@postgresql.org'
Subject: RE: [GENERAL] Need help on triggers - postgres 9.1.2
Many Than
On Thu, May 22, 2014 at 2:41 AM, Sameer Kumar wrote:
> Hi,
>
> I am designing backup strategy for a PostgreSQL database (v9.3). I have a
> scenario for recovery of tablespaces:
>
> 1. Backup of whole database (including individual tablespaces which are
> stored on different disks) has been taken a
On Wed, May 21, 2014 at 7:48 PM, Joe Van Dyk wrote:
> On Wednesday, May 21, 2014, Jeff Janes wrote:
>
>>
>> On Wed, May 21, 2014 at 1:11 PM, Joe Van Dyk wrote:
>>
>>> I came across
>>> http://bonesmoses.org/2014/05/14/foreign-keys-are-not-free/
>>> which seems to indicate so.
>>>
>>> When I run
Jeff Janes writes:
> On Wed, May 21, 2014 at 7:48 PM, Joe Van Dyk wrote:
>> I was expecting that the RI update triggers would have a "when (new.key is
>> distinct from old.key)" condition on them, which would mean that the number
>> of referencing tables wouldn't matter.
> But that condition is
On Thu, May 22, 2014 at 10:52 AM, Tom Lane wrote:
> Jeff Janes writes:
>> On Wed, May 21, 2014 at 7:48 PM, Joe Van Dyk wrote:
>>> I was expecting that the RI update triggers would have a "when (new.key is
>>> distinct from old.key)" condition on them, which would mean that the number
>>> of refe
Hi,
time and again I need to build indexes. If they are big, that generates
a lot of WAL data that needs to be replicated to streaming replication
slaves. Usually these slaves don't lag behind noticeably. So, the
application often reads from them. Well, unless I build indexes and,
thus, create a h
Joe Van Dyk writes:
> On Thu, May 22, 2014 at 10:52 AM, Tom Lane wrote:
>> FWIW, I profiled this example (after cranking it up to 500 target tables
>> just because). AFAICT the primary component of the runtime increase is
>> query startup overhead associated with the increased number of target
>
On 05/22/2014 11:25 AM, Torsten Förtsch wrote:
Hi,
time and again I need to build indexes. If they are big, that generates
a lot of WAL data that needs to be replicated to streaming replication
slaves. Usually these slaves don't lag behind noticeably. So, the
application often reads from them.
On 5/22/2014 11:46 AM, Joshua D. Drake wrote:
This does not appear the domain of PostgreSQL as much as the domain of
your OS and network layer.
I think he's asking for a throttle on create index, so OTHER WAL
activity would proceed at full speed, but the CREATE INDEX would somehow
constrain
On Thu, May 22, 2014 at 11:46 AM, Joshua D. Drake wrote:
>
> On 05/22/2014 11:25 AM, Torsten Förtsch wrote:
>
>>
>> Hi,
>>
>> time and again I need to build indexes. If they are big, that generates
>> a lot of WAL data that needs to be replicated to streaming replication
>> slaves. Usually these s
On 05/22/2014 12:04 PM, John R Pierce wrote:
On 5/22/2014 11:46 AM, Joshua D. Drake wrote:
This does not appear the domain of PostgreSQL as much as the domain of
your OS and network layer.
I think he's asking for a throttle on create index, so OTHER WAL
activity would proceed at full speed,
On 22/05/14 21:05, Jeff Janes wrote:
> time and again I need to build indexes. If they are big, that
> generates
> a lot of WAL data that needs to be replicated to streaming
> replication
> slaves. Usually these slaves don't lag behind noticeably. So, the
>
On 5/22/2014 12:31 PM, Torsten Förtsch wrote:
That's what I want, to throttle the rate at which WAL is generated by
maintenance operations.
I take it, there is no such thing by now. Would it be a useful addition?
I am not sure if I have the time to implement it. I have had a cursory
look at the
Torsten Förtsch wrote:
> That's what I want, to throttle the rate at which WAL is generated by
> maintenance operations.
>
> I take it, there is no such thing by now. Would it be a useful addition?
Uh. See this thread:
http://www.postgresql.org/message-id/ca+u5nmlfxbghq1vlsebhyemjhxz_ohskufdu6_
25 matches
Mail list logo
