subject:"\[GENERAL\] Linux"

Re: [GENERAL] Linux equivalent library for "postgres.lib" from Windows

2016-11-10 Thread David Guyot

If you are looking for the name of the package providing the postgres
library, it will probably change over the distros; under Debian, you're
probably looking for libpq5 for the library itself, but I don't know the
name of the package containing debugging symbols for this one.

Depending on your development language, the corresponding package name can be 
different, and there can be a package with debugging symbols.

Regards.

Le mardi 08 novembre 2016 à 05:01 +, Gadamsetty, Kiran a écrit :
> We are depending on postgres.lib while creating a postgre extension for 
> windows. 
> We need to know the equivalent library in Linux to build the same in Linux to 
> get the symbols resolve correctly.
> 
> Any help is appreciated.
> 
> -Kiran G 
-- 
David Guyot
Administrateur système, réseau et télécom / Sysadmin
Europe Camions Interactive / Stockway
Moulin Collot
F-88500 Ambacourt
03 29 30 47 85


signature.asc
Description: This is a digitally signed message part

Re: [GENERAL] Linux equivalent library for "postgres.lib" from Windows

2016-11-09 Thread Gadamsetty, Kiran

We are depending on postgres.lib while creating a postgre extension for 
windows. 
We need to know the equivalent library in Linux to build the same in Linux to 
get the symbols resolve correctly.

Any help is appreciated.

-Kiran G 



-Original Message-
From: Michael Paquier [mailto:michael.paqu...@gmail.com] 
Sent: Tuesday, November 08, 2016 9:21 AM
To: Gadamsetty, Kiran 
Cc: pgsql-general@postgresql.org; Kumar, Sunil(RM engineering) 

Subject: Re: [GENERAL] Linux equivalent library for "postgres.lib" from Windows

On Mon, Nov 7, 2016 at 2:28 PM, Gadamsetty, Kiran  
wrote:
> I am new to the product and in windows “postgres.lib” provides certain 
> functions which we are using in windows for creating extensions.
>
> Now I am porting the project to Linux and there no straight library 
> with this name in Linux binaries packages.
>
> Can someone please advise the equivalent library for postgres.lib in Linux?

There is no need to go down to this level of details perhaps? You could just 
use the PGXS infrastructure to guess it for you.
--
Michael

-- 
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] Linux equivalent library for "postgres.lib" from Windows

2016-11-08 Thread Albe Laurenz

John R Pierce wrote:
>> I am new to the product and in windows “postgres.lib” provides certain 
>> functions which we are
>> using in windows for creating extensions.
>> 
>> Now I am porting the project to Linux and there no straight library with 
>> this name in Linux
>> binaries packages.
>> 
>> Can someone please advise the equivalent library for postgres.lib in Linux?
> 
> I am not sure what this postgres.lib is, what are the functions you're using ?

With MSVC, you have to link with the mylibrary.lib file if you want to use
functions from the shared library mylibrary.dll.
This is not necessary on Linux, where references to a shared library are 
resolved
at load time.

So the answer to the original question is that there is no replacement
for postgres.lib on Linux because you don't need it to link with PostgreSQL.
It is enough to #include the required PostgreSQL headers during compilation.

Some information on how to link on Linux can be found here:
https://www.postgresql.org/docs/current/static/xfunc-c.html#DFUNC
But as others have remarked, using PGXS is much better than doing
it by hand.

Yours,
Laurenz Albe

-- 
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] Linux equivalent library for "postgres.lib" from Windows

2016-11-07 Thread Michael Paquier

On Tue, Nov 8, 2016 at 1:29 PM, John R Pierce  wrote:
> I am not sure what this postgres.lib is, what are the functions you're using
> ?

It contains references to all the exposed functions of the backend on
Windows. Using something like dumpbin /exports postgres.lib would show
exactly that if I recall correctly. But, anyway, what Kiran is looking
for here is to build his stuff via PGXS.
-- 
Michael


-- 
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] Linux equivalent library for "postgres.lib" from Windows

2016-11-07 Thread John R Pierce


On 11/7/2016 7:51 PM, Michael Paquier wrote:

There is no need to go down to this level of details perhaps? You
could just use the PGXS infrastructure to guess it for you.


+1 I forgot to mention PGXS, that provides a portable method of 
building server-side extensions.


See https://www.postgresql.org/docs/current/static/extend-pgxs.html


--
john r pierce, recycling bits in santa cruz



--
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] Linux equivalent library for "postgres.lib" from Windows

2016-11-07 Thread John R Pierce


On 11/6/2016 9:28 PM, Gadamsetty, Kiran wrote:


I am new to the product and in windows “postgres.lib” provides certain 
functions which we are using in windows for creating extensions.


Now I am porting the project to Linux and there no straight library 
with this name in Linux binaries packages.


Can someone please advise the equivalent library for postgres.lib in 
Linux?




I am not sure what this postgres.lib is, what are the functions you're 
using ?


libpq.so is the standard postgres client library.  it provides the 
PQxx functions documented here, 
https://www.postgresql.org/docs/current/static/libpq.html


or are you talking about the SPI_x functions used by C functions 
being called within postgresql ?






--
john r pierce, recycling bits in santa cruz

Re: [GENERAL] Linux equivalent library for "postgres.lib" from Windows

2016-11-07 Thread Michael Paquier

On Mon, Nov 7, 2016 at 2:28 PM, Gadamsetty, Kiran
 wrote:
> I am new to the product and in windows “postgres.lib” provides certain
> functions which we are using in windows for creating extensions.
>
> Now I am porting the project to Linux and there no straight library with
> this name in Linux binaries packages.
>
> Can someone please advise the equivalent library for postgres.lib in Linux?

There is no need to go down to this level of details perhaps? You
could just use the PGXS infrastructure to guess it for you.
-- 
Michael


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[GENERAL] Linux equivalent library for "postgres.lib" from Windows

2016-11-07 Thread Gadamsetty, Kiran

Hi,

I am new to the product and in windows "postgres.lib" provides certain 
functions which we are using in windows for creating extensions.
Now I am porting the project to Linux and there no straight library with this 
name in Linux binaries packages.

Can someone please advise the equivalent library for postgres.lib in Linux?

Thanks,
Kiran G

Re: [GENERAL] Linux replication to FreeBSD problem

2014-08-20 Thread Jov

Yes,it is locale problem.
I do some more testing,and find that in my DB locale which is
zh_CN.UTF-8,the indexes on FreeBSD slave can works if the indexed data is
lower case ascii,it can't find data contain upper case.

Explicit set the column collate to "C" can solve the problem.
I will recreate all the index with collate "C".

Thanks very much!

Jov
blog: http:amutu.com/blog 


2014-08-20 23:36 GMT+08:00 Tom Lane :

> Adrian Klaver  writes:
> > On 08/20/2014 07:53 AM, Jov wrote:
> >> I setup a PG 9.3.5 master on CentOS 6 x86_64,and 2 screaming replicaton
> >> slaves,one on CentOS6 x86_64,the other on FreeBSD 10 amd64.
> >> The replication work fine for a week,But today I find a problem on sql
> >> running on FreeBSD:simple sql use index do not return result.If I
> >> disable the index ,use seqscan,then I can get correct result.
>
> > I would say FreeBSD is not similar enough to Linux(CentOS) to make this
> > work reliably with binary replication.
>
> The most likely theory as to the source of the problem is that the locale
> names used by the CentOS machine are not recognized by the FreeBSD OS,
> and/or imply slightly different sort orderings.  So a text index that's
> correctly sorted according to the CentOS machine is not correctly sorted
> according to FreeBSD, leading to search failures.
>
> You could probably make this case work reliably if you used C locale on
> both systems; the behavior of that is pretty portable.
>
> regards, tom lane
>
>
> --
> 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] Linux replication to FreeBSD problem

2014-08-20 Thread Tom Lane

Adrian Klaver  writes:
> On 08/20/2014 07:53 AM, Jov wrote:
>> I setup a PG 9.3.5 master on CentOS 6 x86_64,and 2 screaming replicaton
>> slaves,one on CentOS6 x86_64,the other on FreeBSD 10 amd64.
>> The replication work fine for a week,But today I find a problem on sql
>> running on FreeBSD:simple sql use index do not return result.If I
>> disable the index ,use seqscan,then I can get correct result.

> I would say FreeBSD is not similar enough to Linux(CentOS) to make this 
> work reliably with binary replication.

The most likely theory as to the source of the problem is that the locale
names used by the CentOS machine are not recognized by the FreeBSD OS,
and/or imply slightly different sort orderings.  So a text index that's
correctly sorted according to the CentOS machine is not correctly sorted
according to FreeBSD, leading to search failures.

You could probably make this case work reliably if you used C locale on
both systems; the behavior of that is pretty portable.

regards, tom lane

-- 
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] Linux replication to FreeBSD problem

2014-08-20 Thread Adrian Klaver


On 08/20/2014 07:53 AM, Jov wrote:

I setup a PG 9.3.5 master on CentOS 6 x86_64,and 2 screaming replicaton
slaves,one on CentOS6 x86_64,the other on FreeBSD 10 amd64.
The replication work fine for a week,But today I find a problem on sql
running on FreeBSD:simple sql use index do not return result.If I
disable the index ,use seqscan,then I can get correct result.




So,Is this a un-support replication method?


https://wiki.postgresql.org/wiki/Binary_Replication_Tutorial#5_Minutes_to_Simple_Replication

You must have the right setup to make this work:

2 servers with similar operating systems (e.g both Linux 64-bit).

I would say FreeBSD is not similar enough to Linux(CentOS) to make this 
work reliably with binary replication.




Jov
blog: http:amutu.com/blog 



--
Adrian Klaver
adrian.kla...@aklaver.com


--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[GENERAL] Linux replication to FreeBSD problem

2014-08-20 Thread Jov

I setup a PG 9.3.5 master on CentOS 6 x86_64,and 2 screaming replicaton
slaves,one on CentOS6 x86_64,the other on FreeBSD 10 amd64.
The replication work fine for a week,But today I find a problem on sql
running on FreeBSD:simple sql use index do not return result.If I disable
the index ,use seqscan,then I can get correct result.

psql (9.3.5)
Type "help" for help.^
xx=> explain analyze verbose select order_id from orders where order_id =
'AAGJfwJYUzD3';
 QUERY PLAN


 Bitmap Heap Scan on public.orders  (cost=4.47..31.06 rows=7 width=17)
(actual time=0.317..0.317 rows=0 loops=1)
   Output: order_id
   Recheck Cond: ((orders.order_id)::text = 'AAGJfwJYUzD3'::text)
   ->  Bitmap Index Scan on orders_order_id_idx  (cost=0.00..4.47 rows=7
width=0) (actual time=0.252..0.252 rows=0 loops=1)
 Index Cond: ((orders.order_id)::text = 'AAGJfwJYUzD3'::text)
 Total runtime: 0.753 ms
(6 rows)

xx=> set enable_indexonlyscan to f;
SET
xx=> set enable_indexscan to f;
SET
xx=> set enable_bitmapscan to f;
SET
forex=> explain analyze verbose select order_id from orders where order_id
= 'AAGJfwJYUzD3';
 QUERY PLAN

-
 Seq Scan on public.orders  (cost=0.00..2185.69 rows=7 width=17) (actual
time=70.003..71.238 rows=1 loops=1)
   Output: order_id
   Filter: ((orders.order_id)::text = 'AAGJfwJYUzD3'::text)
   Rows Removed by Filter: 63481
 Total runtime: 71.379 ms
(5 rows)

So,Is this a un-support replication method?

Jov
blog: http:amutu.com/blog

Re: [GENERAL] Linux vs FreeBSD

2014-04-11 Thread D'Arcy J.M. Cain

On Fri, 11 Apr 2014 17:15:28 +0300
Achilleas Mantzios  wrote:
> pl/java has nothing to do with this. The argument against using
> packages/ports for postgresql upgrades, is that upgrades in general
> involve :
> - reading HISTORY thoroughly and understanding every bit of it,
> especially the migration part, and the changes part

Do this before installing anything.

> - backing up the current database

Also this.

> - installing the new binaries

This is the only thing that the ports or pkgsrc (NetBSD) facility does
for you.

> - running pg_upgrade
> - solving problems that pg_upgrade detects and trying again
> - testing your in house C/Java/etc... functions
> - testing your whole app + utilities against the new version

After installing the upgrade all of this has to be done.  None of it is
going to be done by ports/pkgsrc/apt-get or any other install
facility including your own brain sweat.  All ports/pkgsrc does for you
is the install part.

> Now, tell me, how much of this can
> the /usr/ports/databases/postgresqlXX-server port can do? Would you

Step 3.  Period.

> trust the system to do this for you in an automated maybe weekly  pkg
> upgrade task that would handle e.g. cdrecord and postgresql-xxx in
> the same manner ?

I wouldn't trust any system to blindly install any program I certainly
wouldn't automate any upgrades on a production server.  The most I
would do automatically is build the latest package for manual
installation.

> Now about writing ports, i can say to you this is a PITA. Its a great
> concept, but you must truly commit to having a part of your life slot
> maintaining the port you submitted. This could be fun at first, but
> in the long run, this is not easy.

Why?  Once you submit your port to the community you could update when
you could or poke the community to do it for you.  All hail open source.

-- 
D'Arcy J.M. Cain  |  Democracy is three wolves
http://www.druid.net/darcy/|  and a sheep voting on
+1 416 788 2246 (DoD#0082)(eNTP)   |  what's for dinner.
IM: da...@vex.net, VoIP: sip:da...@druid.net

-- 
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] Linux vs FreeBSD

2014-04-11 Thread Achilleas Mantzios

On 11/04/2014 15:05, Alban Hertroys wrote:
Although it is getting a bit specific, would you care to elaborate why you would advice strongly against using ports or packages for Postgres on FreeBSD? Because that’s a rather strong statement
you’re making and so far the only argument I’ve seen is that there is no port for pl/java. I’m curious as to why you are so strongly set on custom-compiling Postgres. BTW, isn’t the usual solution
to a missing port to create your own (local) port? I can’t claim I have ever done that (never needed to), but apparently that’s the way to go about it. The obvious benefit is that it will fit in
with the package management system, while you could even provide the port to others if you’d be willing to take responsibility for maintaining that port.

pl/java has nothing to do with this. The argument against using packages/ports
for postgresql
upgrades, is that upgrades in general involve :
- reading HISTORY thoroughly and understanding every bit of it, especially the
migration part,
and the changes part
- backing up the current database
- installing the new binaries
- running pg_upgrade
- solving problems that pg_upgrade detects and trying again
- testing your in house C/Java/etc... functions
- testing your whole app + utilities against the new version

Now, tell me, how much of this can the /usr/ports/databases/postgresqlXX-server
port can do?
Would you trust the system to do this for you in an automated maybe weekly pkg
upgrade task
that would handle e.g. cdrecord and postgresql-xxx in the same manner ?

Now about writing ports, i can say to you this is a PITA. Its a great concept,
but you must truly
commit to having a part of your life slot maintaining the port you submitted.
This could be fun at first,
but in the long run, this is not easy.

Fair enough.

You are welcome :)

Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.

--
Achilleas Mantzios
Head of IT DEV
IT DEPT
Dynacom Tankers Mgmt

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

1 2 3 4 >

1 - 100 of 329 matches

Mail list logo