On 05/22/2012 01:57 PM, Jayashankar K B wrote:
Please let us know why this crash is happening and how we can fix it.
LOG: server process (PID 4016) was terminated by signal 11: Segmentation
fault
If you can't reproduce this crash on a more developer-friendly machine
than your embedded syst
On Tue, May 22, 2012 at 2:24 AM, John R Pierce wrote:
> On 05/21/12 11:03 PM, Greg Simpson wrote:
>>
>> I am trying to get the source XML file for the PostgreSQL installer. This
>> is the BitRock InstallBuilder XML file.
>> Can anyone direct me to the proper place to obtain this installer file?
>
On Tue, May 22, 2012 at 4:51 PM, Jayashankar K B
wrote:
> On writing into this table, a stored procedure is triggered which inserts
> into another table.
> But crash is happening while writing into this financialtransaction table
> once this table has more than 1000 records.
What language is th
But here, the crash is happening right at the insert statement. That is insert
itself is failing.
Unless the insert is successful, stored procedure is not triggered.
Thanks and regards
Jayashankar
-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@po
On Tue, May 22, 2012 at 8:23 PM, Jayashankar K B
wrote:
> But here, the crash is happening right at the insert statement. That is
> insert itself is failing.
> Unless the insert is successful, stored procedure is not triggered.
Hmm. I wonder is it possible that going past ID 999 and into a
four-
2012/5/22 Merlin Moncure
> On Mon, May 21, 2012 at 3:39 PM, J.V. wrote:
> >
> > I am banging my head over this. I want to select distinct values from a
> > varchar column and iterate through the values.
> >
> > I want to select the distinct values from this column and loop through
> them
> > (u
On Tue, May 22, 2012 at 5:41 AM, Chris Angelico wrote:
>
> On Tue, May 22, 2012 at 8:23 PM, Jayashankar K B
> wrote:
> > But here, the crash is happening right at the insert statement. That is
> > insert itself is failing.
> > Unless the insert is successful, stored procedure is not triggered.
>
On Tue, May 22, 2012 at 6:03 AM, Dmitriy Igrishin wrote:
>
> Nice color and font ;-)
>
yup -- html formatted emails that I find displeasing get an automatic
response in 'ms comic sans' :-D.
merlin
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your sub
stop sending mail
2012/5/22 Gugu Nomcebo Mthimkhulu
> stop sending mail
>
You must access the link [1] to unsubscribe from this mailing list.
[1] http://www.postgresql.org/mailpref/pgsql-general
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Pe
On 05/22/2012 07:13 AM, Gugu Nomcebo Mthimkhulu wrote:
> stop sending mail
To unsubscribe go here:
http://mail.postgresql.org/mj/mj_wwwusr/domain=postgresql.org?func=lists-long-full&extra=pgsql-general
--
Adrian Klaver
adrian.kla...@gmail.com
--
Sent via pgsql-general mailing list (pgsql-gene
Why jasperserver has been changed from MySQL to PostGreSQL
In previous versions of jasperserver, MySQL was the supporting database but in
the jasperserver 4.5 version it changed to PostGreSQL.
My question is that why jasperserver changed its mind to PostGreSQL. Which of
the features of PostGreSQ
On May 22, 2012, at 7:31 AM, farhad koohbor wrote:
> My question is that why jasperserver changed its mind to PostGreSQL. Which of
> the features of PostGreSQL are powerful than MySQL?
> Could you please give me a clue?
Postgres is more SQL-compliant and tends to work better at larger scale than
> Possibly. You should be able to tell what's taking so much time by
> keeping an eye on your server during the restore. You could set
> log_statement = 'all' (or just 'ddl' if there is significant other
> activity in other databases) during the restore, and keep an eye on
> pg_stat_activity if yo
Hello
I'm implementing HA/failover for my PG nodes. I'm using PG9.0 and async
replication and linux.
Typical problem - if node 1 fails I want the mirror to become active and take
over for the master.
The solution should be able to initiate the failover of the standby and start
re-directing tr
On Saturday, May 19, 2012 04:42:16 PM Clemens Eisserer wrote:
> Hi again,
>
> We are still constantly getting postgresql processes killed by signal
> 9 from time to time, without any idea why or how.
> Syslog seems completly clean.
>
> In case a postgresql process would exceed some restricted res
No one has any ideas or suggestions, or even questions? If someone
needs more information, I'd be happy to provide it.
This problem is absolutely killing me.
On Mon, May 21, 2012 at 2:05 PM, Lonni J Friedman wrote:
> Greetings,
> I have a 4 server postgresql-9.1.3 cluster (one master doing stre
Greetings,
I have a 4 server postgresql-9.1.3 cluster (one master doing streaming
replication to 3 hot standby servers). All of them are running
Fedora-16-x86_64. Last Friday I upgraded the entire cluster from
Fedora-15 with postgresql-9.0.6 to Fedora-16 with postgresql-9.1.3.
I'm finding that I
I'd say to do some monitoring of your machine when this is happening.
vmstat, iostat, iotop, htop, and so on. Are you running out of
memory, a context switch / interrupt storm? IO bound? And so on.
On Tue, May 22, 2012 at 12:20 PM, Lonni J Friedman wrote:
> No one has any ideas or suggestions,
Do the queries here help?
http://wiki.postgresql.org/wiki/Lock_Monitoring
On Tue, May 22, 2012 at 12:42 PM, Lonni J Friedman wrote:
> Greetings,
> I have a 4 server postgresql-9.1.3 cluster (one master doing streaming
> replication to 3 hot standby servers). All of them are running
> Fedora-16-
Thanks for your reply. Unfortunately, those queries don't shed any
light no the problem. The first two return 0 rows, and the third just
returns 12 rows all associated with the query itself, rather than
anything else.
Any other suggestions?
On Tue, May 22, 2012 at 2:56 PM, Scott Marlowe wrote
I'm using postgresql 9.1.3 from debian squeeze-backports with zh_CN.UTF-8
locale, i find my main log (which is
"/var/log/postgresql/postgresql-9.1-main.log") contains "???" which
indicate some sort of charset encoding problem.
But error messages related to pgsql is fine, only other system messages
On Mon, May 21, 2012 at 2:05 PM, Lonni J Friedman wrote:
Greetings,
When I got in this morning, I found
an autovacuum process that had been running since just before the load
spiked,
Autovacuum might need to set the freeze bit very first time it runs. I recall
hearing advice about running a
23 matches
Mail list logo
