[GENERAL] Postgres crash during Stored procedure execution
Hi, We are facing one database crash issue because of stored procedures. When the stored procedure with a set of values is executed the first time, it works fine. If the same stored procedure is executed with same set of values once more, the database crashes with the error WARNING: terminating connection because of crash of another server process DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. HINT: In a moment you should be able to reconnect to the database and repeat your command. This is what we have in the stored procedure: SELECT * FROM TEST(1, 1) Two values are being passed to the stored procedure. First one is just a number and second value is an ID which has foreign key constraint. Because of the foreign key constraint, the foreign key violation error is expected. But why should the server crash because of this violation? Please let me know what we are missing. Thanks and Regards Jayashankar Larsen Toubro Limited www.larsentoubro.com This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
Re: [GENERAL] Postgres process is crashing continously in 9.1.1
We can understand the difference in shared buffer size as the Windows PC has
2GB of RAM and the board has 256MB of RAM.
So please let us know if this shared buffer parameter has any relation to the
problem we are facing.
Thanks and Regards
Jayashankar
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Jayashankar K B
Sent: Tuesday, May 22, 2012 11:27 AM
To: pgsql-general@postgresql.org
Subject: [GENERAL] Postgres process is crashing continously in 9.1.1
Hi,
We are using Postgres 9.1.1 on a board with Coldfire controller.
The postgres processes are crashing and restarting upon executing a particular
instruction and it keeps repeating. Even when we tried with Postgres 9.1.3,
same problem happens.
It works fine until the FINANCIALTRANSACTIONID reaches 1000.
But the same setup is working fine on a windows PC. We have tried to compare
the configuration differences between windows PC and the board and found that
only difference is the Shared Buffers which is 32 on the PC and 24 on the board.
I am pasting the server log from the board here.
The line highlighted in yellow is the instruction which is causing the crash.
Please let us know why this crash is happening and how we can fix it.
LOG: redo starts at 0/D9B75B4
LOG: record with zero length at 0/D9BBE5C
LOG: redo done at 0/D9BBE22
LOG: last completed transaction was at log time 2012-05-22 02:22:26.641488+00
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
ERROR: duplicate key value violates unique constraint
financialtransaction_pkey
DETAIL: Key (financialtransactionid)=(1004) already exists.
STATEMENT: Insert into FINANCIALTRANSACTION
(ATTENDANT,ENGINEHOUR,RECEIPTPRINTED,FINANCIALTRANSACTIONID) values
('0','0.0','0','1004')
LOG: server process (PID 4016) was terminated by signal 11: Segmentation fault
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited abnormally
and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat
your command.
FATAL: poll() failed in statistics collector: Unknown error 516
LOG: statistics collector process (PID 3962) exited with exit code 1
LOG: all server processes terminated; reinitializing
LOG: database system was interrupted; last known up at 2012-05-22 02:22:29 UTC
LOG: database system was not properly shut down; automatic recovery in progress
LOG: consistent recovery state reached at 0/D9BBEAA
LOG: redo starts at 0/D9BBEAA
LOG: record with zero length at 0/D9C07FA
LOG: redo done at 0/D9C07C0
LOG: last completed transaction was at log time 2012-05-22 02:23:05.372245+00
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
ERROR: duplicate key value violates unique constraint
financialtransaction_pkey
DETAIL: Key (financialtransactionid)=(1004) already exists.
STATEMENT: Insert into FINANCIALTRANSACTION
(ATTENDANT,ENGINEHOUR,RECEIPTPRINTED,FINANCIALTRANSACTIONID) values
('0','0.0','0','1004')
LOG: server process (PID 4098) was terminated by signal 11: Segmentation fault
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited abnormally
and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat
your command.
FATAL: poll() failed in statistics collector: Unknown error 516
LOG: statistics collector process (PID 4035) exited with exit code 1
LOG: all server processes terminated; reinitializing
LOG: database system was interrupted; last known up at 2012-05-22 02:23:08 UTC
LOG: database system was not properly shut down; automatic recovery in progress
LOG: consistent recovery state reached at 0/D9C0848
LOG: redo starts at 0/D9C0848
LOG: record with zero length at 0/D9C5218
LOG: redo done at 0/D9C51DE
LOG: last completed transaction was at log time 2012-05-22 02:23:49.659502+00
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
Thanks and Regards
Jayashankar
Larsen Toubro Limited
www.larsentoubro.com
This Email may contain confidential or privileged information for the intended
recipient (s). If you are not the intended recipient, please do not use or
disseminate the information, notify the sender and delete it from your system.
Earth Day. Every Day.
Larsen Toubro Limited
www.larsentoubro.com
This Email may contain confidential or privileged information for the intended
recipient (s). If you are not the intended recipient, please do not use or
disseminate the information
Re: [GENERAL] Postgres process is crashing continously in 9.1.1
Yes the board has the embedded 68k architecture based Freescale Coldfire processor. The board has a custom built Linux based on the kernel 2.6.38 The database is stored on an SD card of 4GB capacity. This is the table we have. CREATE TABLE financialtransaction ( FINANCIALTRANSACTIONID BIGINT NOT NULL PRIMARY KEY, TIME_STAMP TIMESTAMP, ATTENDANTSMALLINT, RECEIPTPRINTEDBOOLEAN DEFAULT FALSE, ODOMETER VARCHAR(20), ENGINEHOUR NUMERIC(9,2), CONSTRAINT financialtransaction_pkey PRIMARY KEY (FINANCIALTRANSACTIONID ) ) WITH ( OIDS=FALSE ); ALTER TABLE financialtransaction OWNER TO postgres; 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. Please let me know if you need any other information. Thanks and Regards Jayashankar -Original Message- From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of John R Pierce Sent: 22 May 2012 PM 12:00 To: pgsql-general@postgresql.org Subject: Re: [GENERAL] Postgres process is crashing continously in 9.1.1 On 05/21/12 11:05 PM, Jayashankar K B wrote: board with Coldfire controller. what is this board? Coldfire is the embedded 68k-like Freescale processor? what operating system is this under? what sort of storage does this embedded system use for the database? telling us FINANCIALWHATEVERID 1000 doesn't really do us much good since we have no idea what your database looks like, or what your code is doing. the log seems to indicate there was a constraint violation just before the exception hit. -- john r pierceN 37, W 122 santa cruz ca mid-left coast -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general Larsen Toubro Limited www.larsentoubro.com This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. Earth Day. Every Day. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Postgres process is crashing continously in 9.1.1
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...@postgresql.org] On Behalf Of Chris Angelico Sent: Tuesday, May 22, 2012 3:10 PM To: pgsql-general@postgresql.org Subject: Re: [GENERAL] Postgres process is crashing continously in 9.1.1 On Tue, May 22, 2012 at 4:51 PM, Jayashankar K B jayashankar...@lnties.com 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 the stored procedure written in? Is it possible that it's that procedure that segfaults? Postgres experts, do stored procedure segfaults bring down the backend process like that? ChrisA -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general Larsen Toubro Limited www.larsentoubro.com This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. Earth Day. Every Day. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Postgres process is crashing continously in 9.1.1
Hi,
We are using Postgres 9.1.1 on a board with Coldfire controller.
The postgres processes are crashing and restarting upon executing a particular
instruction and it keeps repeating. Even when we tried with Postgres 9.1.3,
same problem happens.
It works fine until the FINANCIALTRANSACTIONID reaches 1000.
But the same setup is working fine on a windows PC. We have tried to compare
the configuration differences between windows PC and the board and found that
only difference is the Shared Buffers which is 32 on the PC and 24 on the board.
I am pasting the server log from the board here.
The line highlighted in yellow is the instruction which is causing the crash.
Please let us know why this crash is happening and how we can fix it.
LOG: redo starts at 0/D9B75B4
LOG: record with zero length at 0/D9BBE5C
LOG: redo done at 0/D9BBE22
LOG: last completed transaction was at log time 2012-05-22 02:22:26.641488+00
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
ERROR: duplicate key value violates unique constraint
financialtransaction_pkey
DETAIL: Key (financialtransactionid)=(1004) already exists.
STATEMENT: Insert into FINANCIALTRANSACTION
(ATTENDANT,ENGINEHOUR,RECEIPTPRINTED,FINANCIALTRANSACTIONID) values
('0','0.0','0','1004')
LOG: server process (PID 4016) was terminated by signal 11: Segmentation fault
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited abnormally
and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat
your command.
FATAL: poll() failed in statistics collector: Unknown error 516
LOG: statistics collector process (PID 3962) exited with exit code 1
LOG: all server processes terminated; reinitializing
LOG: database system was interrupted; last known up at 2012-05-22 02:22:29 UTC
LOG: database system was not properly shut down; automatic recovery in progress
LOG: consistent recovery state reached at 0/D9BBEAA
LOG: redo starts at 0/D9BBEAA
LOG: record with zero length at 0/D9C07FA
LOG: redo done at 0/D9C07C0
LOG: last completed transaction was at log time 2012-05-22 02:23:05.372245+00
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
ERROR: duplicate key value violates unique constraint
financialtransaction_pkey
DETAIL: Key (financialtransactionid)=(1004) already exists.
STATEMENT: Insert into FINANCIALTRANSACTION
(ATTENDANT,ENGINEHOUR,RECEIPTPRINTED,FINANCIALTRANSACTIONID) values
('0','0.0','0','1004')
LOG: server process (PID 4098) was terminated by signal 11: Segmentation fault
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited abnormally
and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat
your command.
FATAL: poll() failed in statistics collector: Unknown error 516
LOG: statistics collector process (PID 4035) exited with exit code 1
LOG: all server processes terminated; reinitializing
LOG: database system was interrupted; last known up at 2012-05-22 02:23:08 UTC
LOG: database system was not properly shut down; automatic recovery in progress
LOG: consistent recovery state reached at 0/D9C0848
LOG: redo starts at 0/D9C0848
LOG: record with zero length at 0/D9C5218
LOG: redo done at 0/D9C51DE
LOG: last completed transaction was at log time 2012-05-22 02:23:49.659502+00
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
Thanks and Regards
Jayashankar
Larsen Toubro Limited
www.larsentoubro.com
This Email may contain confidential or privileged information for the intended
recipient (s). If you are not the intended recipient, please do not use or
disseminate the information, notify the sender and delete it from your system.
Earth Day. Every Day.
[GENERAL] Significance of Postgres (version 9.1.1) Compilation parameters - Performance
Hi All, Could anyone explain me the significance of the following compile time parameters ? 1. --disable-integer-datetimes 2. --disable-float4-byval 3. --disable-float8-byval Do they have any effect on performance of postgres w.r.t speed of database insert/select, amount of CPU used during insert/select ? How can I know the default compile time parameter values? The environment in which we are trying to run postgres is a freescale MCF54xx controller based board having 512MB RAM, 2GB memory with custom built Linux (32-bit environment). Thanks and Regards Jayashankar Larsen Toubro Limited www.larsentoubro.com This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. Earth Day. Every Day.
Re: [GENERAL] Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8
Ok. I did a manual patch and it Postgres 9.1.1 compiled for me without using the --disable-spinlocks option. Thanks a lot for the patch. :) By the way, could you please point me to the explanation on the significance of spinlocks for Postgres? Thanks and Regards Jayashankar -Original Message- From: Tom Lane [mailto:t...@sss.pgh.pa.us] Sent: 25 February 2012 PM 12:54 To: Jayashankar K B Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8 Jayashankar K B jayashankar...@lnties.com writes: I tried to apply the patch. I succeeded in patching configure, configure.in and src/include/pg_config.h.in files. But while applying the patch for src/include/storage/s_lock.h , I am getting an error. That patch should apply exactly to 9.1.0 or later. I think either you messed up copying the patch from the web page (note that patch is not forgiving about white space...) or else perhaps fooling with the file names messed it up. You shouldn't have to modify the file taken from the patch link at all. The right way to do it is to cd into the top source directory and use patch -p1 patchfile which will tell patch how much of the filename to pay attention to (viz, not the a/ or b/ parts). If you get too frustrated, just wait till Monday and grab 9.1.3. regards, tom lane Larsen Toubro Limited www.larsentoubro.com This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8
Hi Tom, I tried to apply the patch. I succeeded in patching configure, configure.in and src/include/pg_config.h.in files. But while applying the patch for src/include/storage/s_lock.h , I am getting an error. This is how I am doing the patch, 1. I copied the diff output given in the link mentioned in the below email. 2. Changed the file names appropriately (patch file path is different from source file path. But I have initialized --- and +++ appropriately 3. Executed the patch command in the Postgres 9.1.1 directory as patch src/include/storage/s_lock.h -i s_lock.h_Patch 4. Got the following output Hunk #1 succeeded at 252 with fuzz 1. Hunk #2 FAILED at 292. 1 out of 2 hunks FAILED -- saving rejects to file src/include/storage/s_lock.h.rej Thought of doing the failed patch manually. But couldn't understand what to do. Please let me know what I am doing wrong and what I should be doing. Thanks and Regards Jayashankar -Original Message- From: Tom Lane [mailto:t...@sss.pgh.pa.us] Sent: 24 February 2012 AM 09:20 To: Jayashankar K B Cc: pgsql-general@postgresql.org; pgsql-performa...@postgresql.org Subject: Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8 Jayashankar K B jayashankar...@lnties.commailto:jayashankar...@lnties.com writes: Hi All, I am trying to compile Postgres Source code for ARM cortex A8 architecture. While compiling, I got an error message which read selected processor does not support `swpb r4,r4,[r3]' One of the Postgres forums at the location http://postgresql.1045698.n5.nabble.com/BUG-6331-Cross-compile-error-aborts-Works-if-disable-spinlock-is-used-td5068738.html; Mentioned that by using -disable-spinlocks, we can overcome the error at the cost of performance. I did the same and it compiled successfully. But the INSTALL guide in Postgres source code mentioned that I should inform the Postgres community in case I am forced to use -disable spinlocks to let the code compile. Hence this email. So please suggest me what I should do now. Try this patch: http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=068e08eebbb2204f525647daad3fe15063b77820 BTW, please don't cross-post to multiple PG mailing lists; there's very seldom a good reason to do that. regards, tom lane Larsen Toubro Limited www.larsentoubro.com This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
[GENERAL] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8
Hi All, I am trying to compile Postgres Source code for ARM cortex A8 architecture. While compiling, I got an error message which read selected processor does not support `swpb r4,r4,[r3]' One of the Postgres forums at the location http://postgresql.1045698.n5.nabble.com/BUG-6331-Cross-compile-error-aborts-Works-if-disable-spinlock-is-used-td5068738.html; Mentioned that by using -disable-spinlocks, we can overcome the error at the cost of performance. I did the same and it compiled successfully. But the INSTALL guide in Postgres source code mentioned that I should inform the Postgres community in case I am forced to use -disable spinlocks to let the code compile. Hence this email. So please suggest me what I should do now. What sort of performance penalty will be there if I use this option? What actually is the significance of this parameter? Please guide me. This is the configure command I used ./configure CC=/opt/toolchain/bin/armv7l-timesys-linux-gnueabi-gcc --target=armv7l-timesys-linux-gnueabi --prefix=/home/jayashankar/WorkingDirectory/Postgres9.1_Cortex --host=x86_64-unknown-linux-gnu CFLAGS='-march=armv7-a -mtune=cortex-a8 -mfpu=vfpv3 -mthumb' --disable-spinlocks Thanks and Regards Jayashankar Larsen Toubro Limited www.larsentoubro.com This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
[GENERAL] Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8
Hi Tom, Sorry about the cross-post. I am not aware of the procedures for patch etc. Could you please tell me how to use the patch ? I have already compiled and got the postgres server. So please let me know the process of patching or kindly point me to a link which explain this. Thanks and Regards Jayashankar -Original Message- From: Tom Lane [mailto:t...@sss.pgh.pa.us] Sent: 24 February 2012 AM 09:20 To: Jayashankar K B Cc: pgsql-general@postgresql.org; pgsql-performa...@postgresql.org Subject: Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8 Jayashankar K B jayashankar...@lnties.com writes: Hi All, I am trying to compile Postgres Source code for ARM cortex A8 architecture. While compiling, I got an error message which read selected processor does not support `swpb r4,r4,[r3]' One of the Postgres forums at the location http://postgresql.1045698.n5.nabble.com/BUG-6331-Cross-compile-error-aborts-Works-if-disable-spinlock-is-used-td5068738.html; Mentioned that by using -disable-spinlocks, we can overcome the error at the cost of performance. I did the same and it compiled successfully. But the INSTALL guide in Postgres source code mentioned that I should inform the Postgres community in case I am forced to use -disable spinlocks to let the code compile. Hence this email. So please suggest me what I should do now. Try this patch: http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=068e08eebbb2204f525647daad3fe15063b77820 BTW, please don't cross-post to multiple PG mailing lists; there's very seldom a good reason to do that. regards, tom lane Larsen Toubro Limited www.larsentoubro.com This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Postgres 9.1 package for i.MX51X processor from Freescale
Hi, Is there a ready postgres 9.1 Package for the i.MX51X processor (ARM Cortex architecture) available or do I need to compile the Postgres source myself ? I need it for a board having the i.MX51 processor and Linux (a variant of Debian distribution based on Linux kernel 2.6.35). If I need to compile postgres source, then what CC Flags should I use for this particular processor architecture ? If any ideas, please share. Thanks and Regards Jay Larsen Toubro Limited www.larsentoubro.com This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
[GENERAL] Postgres 9.1 package for i.MX51X processor from Freescale
Hi, Anybody with any ideas on using Postgres on ARM CORTEX A8 based processors.. ? Thanks! Jay From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Jayashankar K B Sent: 16 February 2012 PM 04:00 To: pgsql-general@postgresql.org Subject: [GENERAL] Postgres 9.1 package for i.MX51X processor from Freescale Hi, Is there a ready postgres 9.1 Package for the i.MX51X processor (ARM Cortex architecture) available or do I need to compile the Postgres source myself ? I need it for a board having the i.MX51 processor and Linux (one of the latest versions of kernel - yet to decide the exact version). If I need to compile postgres source, then what parameters should I use for this particular processor architecture ? Also, I am yet to find a cross compilation tool chain for this processor. If any ideas, please share. Thanks and Regards Jay Larsen Toubro Limited www.larsentoubro.com This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
[GENERAL] Postgres 9.1 package for i.MX51X processor from Freescale
Hi, Is there a ready postgres 9.1 Package for the i.MX51X processor (ARM Cortex architecture) available or do I need to compile the Postgres source myself ? I need it for a board having the i.MX51 processor and Linux (one of the latest versions of kernel - yet to decide the exact version). If I need to compile postgres source, then what parameters should I use for this particular processor architecture ? Also, I am yet to find a cross compilation tool chain for this processor. If any ideas, please share. Thanks and Regards Jay Larsen Toubro Limited www.larsentoubro.com This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
[GENERAL] Regarding licensing of Postgresql
Hi, We are planning to use Postgres 9.1 in our commercial product having a coldfire m68k architecture based controller on Linux platform. Since ready installer was not present for this architecture, we cross compiled the source code and it is working fine now, though we are yet to do Full-fledged testing on the integration. Now we have a doubt about licensing. What is the licensing process if we want to use postgresql with our proprietary software? Could anyone please throw some light on this ? Thanks and Regards Jayashankar Larsen Toubro Limited www.larsentoubro.com This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
Re: [GENERAL] Regarding licensing of Postgresql
Hi John, Thanks for your swift reply.! the only caveat is if you've linked in any GPL code, such as readline, that can taint your whole project and require you to distribute source code according to the GPL terms. Does that mean, we have to distribute whole source code including our proprietary software source? Thanks and Regards Jayashankar -Original Message- From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of John R Pierce Sent: Monday, December 05, 2011 2:12 PM To: pgsql-general@postgresql.org Subject: Re: [GENERAL] Regarding licensing of Postgresql On 12/05/11 12:23 AM, Jayashankar K B wrote: Now we have a doubt about licensing. What is the licensing process if we want to use postgresql with our proprietary software? Could anyone please throw some light on this ? very simple. PostgreSQL Database Management System (formerly known as Postgres, then as Postgres95) Portions Copyright (c) 1996-2011, PostgreSQL Global Development Group Portions Copyright (c) 1994, The Regents of the University of California Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies. IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN AS IS BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS. include that in your copyright notices, and you're gold. the only caveat is if you've linked in any GPL code, such as readline, that can taint your whole project and require you to distribute source code according to the GPL terms. -- john r pierceN 37, W 122 santa cruz ca mid-left coast -- Sent via pgsql-general mailing list (pgsql-general@postgresql.orgmailto:pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general Larsen Toubro Limited www.larsentoubro.com This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
