On 5/2/20 4:03 PM, TalGloz wrote:
Tom Lane-2 wrote
TalGloz <
glozmantal@
> writes:
I dont understand why the output for Postgres 12
g++ -Wall -Wpointer-arith -Wendif-labels -Wmissing-format-attribute
-Wformat-security -fno-strict-aliasing -fwrapv -O2 -o seal_diff_cpp.o -c
seal_diff_cpp.c
Tom Lane-2 wrote
> TalGloz <
> glozmantal@
> > writes:
>> I dont understand why the output for Postgres 12
>> g++ -Wall -Wpointer-arith -Wendif-labels -Wmissing-format-attribute
>> -Wformat-security -fno-strict-aliasing -fwrapv -O2 -o seal_diff_cpp.o -c
>> seal_diff_cpp.cpp
>> seal_diff_cpp.cpp
On 5/2/20 2:44 PM, TalGloz wrote:
Adrian Klaver-4 wrote
On 5/2/20 2:18 PM, Tom Lane wrote:
TalGloz <
adrian.klaver@
The "include $(PGXS)" is defined in the Makefile. After changig the CXXFLAGS
Hmm, time to clean my glasses.
Have no idea what the below means.
to PG_CXXFLAGS I get:
Adrian Klaver-4 wrote
> On 5/2/20 2:18 PM, Tom Lane wrote:
>> TalGloz <
> glozmantal@
> > writes:
>>> I dont understand why the output for Postgres 12
>>> g++ -Wall -Wpointer-arith -Wendif-labels -Wmissing-format-attribute
>>> -Wformat-security -fno-strict-aliasing -fwrapv -O2 -o seal_diff_cpp.o
On 5/2/20 2:18 PM, Tom Lane wrote:
TalGloz writes:
I dont understand why the output for Postgres 12
g++ -Wall -Wpointer-arith -Wendif-labels -Wmissing-format-attribute
-Wformat-security -fno-strict-aliasing -fwrapv -O2 -o seal_diff_cpp.o -c
seal_diff_cpp.cpp
seal_diff_cpp.cpp:2:10: fatal error
TalGloz writes:
> I dont understand why the output for Postgres 12
> g++ -Wall -Wpointer-arith -Wendif-labels -Wmissing-format-attribute
> -Wformat-security -fno-strict-aliasing -fwrapv -O2 -o seal_diff_cpp.o -c
> seal_diff_cpp.cpp
> seal_diff_cpp.cpp:2:10: fatal error: postgres.h: No such file
Adrian Klaver-4 wrote
> On 5/2/20 1:09 PM, TalGloz wrote:
>> Adrian Klaver-4 wrote
>
>>
>> Yes, they were created when using make against Postgres 10 and I clean
>> them
>> every time when I try a different version of Postgres.
>
> Well I'm reaching the end of what I can do. All I have left is t
On 5/2/20 1:09 PM, TalGloz wrote:
Adrian Klaver-4 wrote
Yes, they were created when using make against Postgres 10 and I clean them
every time when I try a different version of Postgres.
Well I'm reaching the end of what I can do. All I have left is that the
examples I have seen use:
#in
Adrian Klaver-4 wrote
> On 5/2/20 1:03 PM, TalGloz wrote:
>> Adrian Klaver-4 wrote
>>> On 5/2/20 12:39 PM, TalGloz wrote:
Adrian Klaver-4 wrote
> On 5/2/20 12:28 PM, TalGloz wrote:
>> I'm trying to upgrade from PostgreSQL 10 to 12 and I need to compile
>> all
>> my
>> manua
On 5/2/20 1:03 PM, TalGloz wrote:
Adrian Klaver-4 wrote
On 5/2/20 12:39 PM, TalGloz wrote:
Adrian Klaver-4 wrote
On 5/2/20 12:28 PM, TalGloz wrote:
I'm trying to upgrade from PostgreSQL 10 to 12 and I need to compile
all
my
manually created C extension functions against PostrgreSQL 12 before
Adrian Klaver-4 wrote
> On 5/2/20 12:39 PM, TalGloz wrote:
>> Adrian Klaver-4 wrote
>>> On 5/2/20 12:28 PM, TalGloz wrote:
I'm trying to upgrade from PostgreSQL 10 to 12 and I need to compile
all
my
manually created C extension functions against PostrgreSQL 12 before
starti
On 5/2/20 12:39 PM, TalGloz wrote:
Adrian Klaver-4 wrote
On 5/2/20 12:28 PM, TalGloz wrote:
I'm trying to upgrade from PostgreSQL 10 to 12 and I need to compile all
my
manually created C extension functions against PostrgreSQL 12 before
starting the upgrade process. I have this Makefile that co
Adrian Klaver-4 wrote
> On 5/2/20 12:28 PM, TalGloz wrote:
>> I'm trying to upgrade from PostgreSQL 10 to 12 and I need to compile all
>> my
>> manually created C extension functions against PostrgreSQL 12 before
>> starting the upgrade process. I have this Makefile that compiles
>> perfectly
>> th
On 5/2/20 12:28 PM, TalGloz wrote:
I'm trying to upgrade from PostgreSQL 10 to 12 and I need to compile all my
manually created C extension functions against PostrgreSQL 12 before
starting the upgrade process. I have this Makefile that compiles perfectly
the seal_diff_cpp.cpp C extension function
I'm trying to upgrade from PostgreSQL 10 to 12 and I need to compile all my
manually created C extension functions against PostrgreSQL 12 before
starting the upgrade process. I have this Makefile that compiles perfectly
the seal_diff_cpp.cpp C extension function against PostgreSQL 10:
MODULES = se
On 5/2/20 11:58 AM, Matthias Apitz wrote:
El día sábado, mayo 02, 2020 a las 08:23:52a. m. -0700, Adrian Klaver escribió:
On 5/2/20 8:02 AM, Paul Förster wrote:
Hi Adrian,
On 02. May, 2020, at 16:59, Adrian Klaver wrote:
2) To create a new base/ you will need to initdb data/ and that is not
Hi Matthias,
> On 02. May, 2020, at 20:58, Matthias Apitz wrote:
> OK, lesson learned: Next time I will do a tar backup of PGDATA after
> the configuration of the cluster and before creating any database in it.
that tar would still contain too much. :-) You really only need the config
files. Al
El día sábado, mayo 02, 2020 a las 08:23:52a. m. -0700, Adrian Klaver escribió:
> On 5/2/20 8:02 AM, Paul Förster wrote:
> > Hi Adrian,
> >
> >> On 02. May, 2020, at 16:59, Adrian Klaver
> >> wrote:
> >> 2) To create a new base/ you will need to initdb data/ and that is not
> >> possible as in
On Sat, May 2, 2020 at 12:31 AM TalGloz wrote:
> Adrian Klaver-4 wrote
> > On 5/1/20 3:39 PM, TalGloz wrote:
> >> Adrian Klaver-4 wrote
> >>> Why not compile them against 11?
> >>>
> >>> Then follow step 5) here:
> >>>
> >>> https://www.postgresql.org/docs/12/pgupgrade.html
>
> 2. How to upgrade
On 5/2/20 12:30 AM, TalGloz wrote:
Adrian Klaver-4 wrote
On 5/1/20 3:39 PM, TalGloz wrote:
Adrian Klaver-4 wrote
Why not compile them against 11?
Then follow step 5) here:
https://www.postgresql.org/docs/12/pgupgrade.html
Step 5 doesn’t actually say how to compile them during the upgrade
p
On 5/2/20 8:02 AM, Paul Förster wrote:
Hi Adrian,
On 02. May, 2020, at 16:59, Adrian Klaver wrote:
2) To create a new base/ you will need to initdb data/ and that is not possible
as initdb will not work on a populated data/.
you do the initdb and then copy the *.conf files from the tar over
Hi Adrian,
> On 02. May, 2020, at 16:59, Adrian Klaver wrote:
> 2) To create a new base/ you will need to initdb data/ and that is not
> possible as initdb will not work on a populated data/.
you do the initdb and then copy the *.conf files from the tar over the newly
created ones. After that,
On 5/2/20 7:30 AM, Matthias Apitz wrote:
El día sábado, mayo 02, 2020 a las 03:23:52p. m. +0200, Paul Förster escribió:
/usr/local/sisis-pap/pgsql <= software with bin, lib64, share, etc...
/data/postgresql11/data <= PGDATA
Exactly, his is the setup above.
I will move /usr/local/sisis-p
Hi Matthias,
> On 02. May, 2020, at 16:30, Matthias Apitz wrote:
>
> El día sábado, mayo 02, 2020 a las 03:23:52p. m. +0200, Paul Förster escribió:
>
>> /usr/local/sisis-pap/pgsql <= software with bin, lib64, share, etc...
>> /data/postgresql11/data <= PGDATA
>
> Exactly, his is the setup
El día sábado, mayo 02, 2020 a las 03:23:52p. m. +0200, Paul Förster escribió:
> /usr/local/sisis-pap/pgsql <= software with bin, lib64, share, etc...
> /data/postgresql11/data <= PGDATA
Exactly, his is the setup above.
I will move /usr/local/sisis-pap/pgsql by tar; and I want to move some
Hi Matthias,
> On 02. May, 2020, at 12:23, Matthias Apitz wrote:
> $ /usr/local/sisis-pap/pgsql/bin/pg_ctl -D /data/prosgresql11/data initdb
I don't get it. Is the setup now as follows
/data/postgresql11 <= software with bin, lib64, share, etc...
/data/postgresql11/data <= PGDATA
or
/u
El día viernes, mayo 01, 2020 a las 10:31:48a. m. +0200, Matthias Apitz
escribió:
> Hi Paul,
>
> El día viernes, mayo 01, 2020 a las 10:23:37a. m. +0200, Paul Förster
> escribió:
>
> >
> > you may have a look at the tar man page. tar in Linux has the
> > --exclude=PATTERN option.
>
> I do k
Adrian Klaver-4 wrote
> On 5/1/20 3:39 PM, TalGloz wrote:
>> Adrian Klaver-4 wrote
>>> Why not compile them against 11?
>>>
>>> Then follow step 5) here:
>>>
>>> https://www.postgresql.org/docs/12/pgupgrade.html
>>
>> Step 5 doesn’t actually say how to compile them during the upgrade
>> process
>>
28 matches
Mail list logo