From 49bdeadcf00025afec8f6486190e64f4c8fbabae Mon Sep 17 00:00:00 2001 From: Yanmei Sun Date: Tue, 1 Jun 2021 13:09:09 +0900 Subject: [PATCH] fix some mistakes in spec files --- SPECS/pg_bulkload-pg10.spec | 196 +++++++-------- SPECS/pg_bulkload-pg11.spec | 226 +++++++++--------- ...lkload-pg12.sepc => pg_bulkload-pg12.spec} | 218 ++++++++--------- SPECS/pg_bulkload-pg13.spec | 2 +- SPECS/pg_bulkload-pg96.spec | 222 ++++++++--------- 5 files changed, 432 insertions(+), 432 deletions(-) rename SPECS/{pg_bulkload-pg12.sepc => pg_bulkload-pg12.spec} (96%) diff --git a/SPECS/pg_bulkload-pg10.spec b/SPECS/pg_bulkload-pg10.spec index a644361..5e63a8a 100644 --- a/SPECS/pg_bulkload-pg10.spec +++ b/SPECS/pg_bulkload-pg10.spec @@ -1,98 +1,98 @@ -# SPEC file for pg_bulkload on PostgreSQL 10 -# Copyright (C) 2009-2021 NIPPON TELEGRAPH AND TELEPHONE CORPORATION - -%define sname pg_bulkload -%define pgmajorversion 10 - -%define _prefix /usr/pgsql-%{pgmajorversion} -%define _libdir %{_prefix}/lib - -Summary: High speed data load utility for PostgreSQL -Name: %{sname} -Version: 3.1.18 -Release: 1%{?dist} -License: BSD -Group: Applications/Databases -# You can get the tarball by following: https://github.com/ossc-db/pg_bulkload/archive/%{version}.tar.gz -Source0: %{sname}-%{version}.tar.gz -URL: http://ossc-db.github.io/pg_bulkload/index.html -BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-%(%{__id_u} -n) - -BuildRequires: postgresql10-devel, postgresql10 -Requires: postgresql10 - - -%description -pg_bulkload provides high-speed data loading capability to PostgreSQL users. - -When we load huge amount of data to a database, it is common situation that data set to be loaded is valid and consistent. For example, dedicated tools are used to prepare such data, providing data validation in advance. In such cases, we'd like to bypass any overheads within database system to load data as quickly as possible. pg_bulkload is developed to help such situations. Therefore, it is not pg_bulkload's goal to provide detailed data validation. Rather, pg_bulkload asumes that loaded data set is validated by separate means. If you're not in such situation, you should use COPY command in PostgreSQL. - - -%prep -rm -rf %{_libdir}/pgxs/src/backend/ - -%setup -n %{sname}-%{version} - -%build -USE_PGXS=1 make %{?_smp_mflags} MAJORVERSION=%{pgmajorversion} - -%install -%define pg_contribdir %{_datadir}/contrib -%define pg_extensiondir %{_datadir}/extension - -rm -rf %{buildroot} - -install -d %{buildroot}%{_bindir} -install -d %{buildroot}%{_libdir} -install -d %{buildroot}%{pg_contribdir} -install -d %{buildroot}%{pg_extensiondir} - -install -m 755 bin/pg_bulkload %{buildroot}%{_bindir}/pg_bulkload -install -m 755 bin/postgresql %{buildroot}%{_bindir}/postgresql -install -m 755 lib/pg_bulkload.so %{buildroot}%{_libdir}/pg_bulkload.so - -install -m 644 lib/pg_bulkload.sql %{buildroot}%{pg_contribdir}/pg_bulkload.sql -install -m 644 lib/uninstall_pg_bulkload.sql %{buildroot}%{pg_contribdir}/uninstall_pg_bulkload.sql -install -m 644 lib/pg_bulkload.control %{buildroot}%{pg_extensiondir}/pg_bulkload.control -install -m 644 lib/pg_bulkload--1.0.sql %{buildroot}%{pg_extensiondir}/pg_bulkload--1.0.sql -install -m 644 lib/pg_bulkload--unpackaged--1.0.sql %{buildroot}%{pg_extensiondir}/pg_bulkload--unpackaged--1.0.sql - -# sample_*.ctl files are needed for rpm users. -# %{sname}-%{version} is the same path with "%setup -n"'s argument. -install -m 644 docs/sample_bin.ctl %{buildroot}%{pg_contribdir}/sample_bin.ctl -install -m 644 docs/sample_csv.ctl %{buildroot}%{pg_contribdir}/sample_csv.ctl - -%files -%defattr(755,root,root,755) -%{_bindir}/pg_bulkload -%{_bindir}/postgresql -%{_libdir}/pg_bulkload.so -%defattr(644,root,root,755) -#%doc README.pg_bulkload -%{pg_contribdir}/pg_bulkload.sql -%{pg_contribdir}/uninstall_pg_bulkload.sql -%{pg_contribdir}/sample_bin.ctl -%{pg_contribdir}/sample_csv.ctl -%{pg_extensiondir}/pg_bulkload.control -%{pg_extensiondir}/pg_bulkload--1.0.sql -%{pg_extensiondir}/pg_bulkload--unpackaged--1.0.sql - -%clean -rm -rf %{buildroot} -rm -rf %{_libdir}/pgxs/src/backend/ - -%changelog -* Tue June 01 2021 - Yanmei Sun 3.1.18-1 -- Update to pg_bulkload 3.1.18 -* Fri Feb 05 2021 - Moon Insung 3.1.17-1 -- Update to pg_bulkload 3.1.17 -* Wed Jan 22 2020 - Moon Insung 3.1.16-1 -- Update to pg_bulkload 3.1.16 -- Warn users of some risks of using parallel/multi-process mode -- Document restriction that pg_bulkload supports only tables of "heap" access method -* Mon Jan 21 2019 - Moon Insung 3.1.15-1 -- Fixed pg_bulkload to mitigate attacks described in CVE-2018-1058 -- Update to pg_bulkload 3.1.15 -* Thu Nov 02 2017 - Moon Insung 3.1.14-1 -- Support PostgreSQL 10 -- Update to pg_bulkload 3.1.14 +# SPEC file for pg_bulkload on PostgreSQL 10 +# Copyright (C) 2009-2021 NIPPON TELEGRAPH AND TELEPHONE CORPORATION + +%define sname pg_bulkload +%define pgmajorversion 10 + +%define _prefix /usr/pgsql-%{pgmajorversion} +%define _libdir %{_prefix}/lib + +Summary: High speed data load utility for PostgreSQL +Name: %{sname} +Version: 3.1.18 +Release: 1%{?dist} +License: BSD +Group: Applications/Databases +# You can get the tarball by following: https://github.com/ossc-db/pg_bulkload/archive/%{version}.tar.gz +Source0: %{sname}-%{version}.tar.gz +URL: http://ossc-db.github.io/pg_bulkload/index.html +BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-%(%{__id_u} -n) + +BuildRequires: postgresql10-devel, postgresql10 +Requires: postgresql10 + + +%description +pg_bulkload provides high-speed data loading capability to PostgreSQL users. + +When we load huge amount of data to a database, it is common situation that data set to be loaded is valid and consistent. For example, dedicated tools are used to prepare such data, providing data validation in advance. In such cases, we'd like to bypass any overheads within database system to load data as quickly as possible. pg_bulkload is developed to help such situations. Therefore, it is not pg_bulkload's goal to provide detailed data validation. Rather, pg_bulkload asumes that loaded data set is validated by separate means. If you're not in such situation, you should use COPY command in PostgreSQL. + + +%prep +rm -rf %{_libdir}/pgxs/src/backend/ + +%setup -n %{sname}-%{version} + +%build +USE_PGXS=1 make %{?_smp_mflags} MAJORVERSION=%{pgmajorversion} + +%install +%define pg_contribdir %{_datadir}/contrib +%define pg_extensiondir %{_datadir}/extension + +rm -rf %{buildroot} + +install -d %{buildroot}%{_bindir} +install -d %{buildroot}%{_libdir} +install -d %{buildroot}%{pg_contribdir} +install -d %{buildroot}%{pg_extensiondir} + +install -m 755 bin/pg_bulkload %{buildroot}%{_bindir}/pg_bulkload +install -m 755 bin/postgresql %{buildroot}%{_bindir}/postgresql +install -m 755 lib/pg_bulkload.so %{buildroot}%{_libdir}/pg_bulkload.so + +install -m 644 lib/pg_bulkload.sql %{buildroot}%{pg_contribdir}/pg_bulkload.sql +install -m 644 lib/uninstall_pg_bulkload.sql %{buildroot}%{pg_contribdir}/uninstall_pg_bulkload.sql +install -m 644 lib/pg_bulkload.control %{buildroot}%{pg_extensiondir}/pg_bulkload.control +install -m 644 lib/pg_bulkload--1.0.sql %{buildroot}%{pg_extensiondir}/pg_bulkload--1.0.sql +install -m 644 lib/pg_bulkload--unpackaged--1.0.sql %{buildroot}%{pg_extensiondir}/pg_bulkload--unpackaged--1.0.sql + +# sample_*.ctl files are needed for rpm users. +# %{sname}-%{version} is the same path with "%setup -n"'s argument. +install -m 644 docs/sample_bin.ctl %{buildroot}%{pg_contribdir}/sample_bin.ctl +install -m 644 docs/sample_csv.ctl %{buildroot}%{pg_contribdir}/sample_csv.ctl + +%files +%defattr(755,root,root,755) +%{_bindir}/pg_bulkload +%{_bindir}/postgresql +%{_libdir}/pg_bulkload.so +%defattr(644,root,root,755) +#%doc README.pg_bulkload +%{pg_contribdir}/pg_bulkload.sql +%{pg_contribdir}/uninstall_pg_bulkload.sql +%{pg_contribdir}/sample_bin.ctl +%{pg_contribdir}/sample_csv.ctl +%{pg_extensiondir}/pg_bulkload.control +%{pg_extensiondir}/pg_bulkload--1.0.sql +%{pg_extensiondir}/pg_bulkload--unpackaged--1.0.sql + +%clean +rm -rf %{buildroot} +rm -rf %{_libdir}/pgxs/src/backend/ + +%changelog +* Tue Jun 01 2021 - Yanmei Sun 3.1.18-1 +- Update to pg_bulkload 3.1.18 +* Fri Feb 05 2021 - Moon Insung 3.1.17-1 +- Update to pg_bulkload 3.1.17 +* Wed Jan 22 2020 - Moon Insung 3.1.16-1 +- Update to pg_bulkload 3.1.16 +- Warn users of some risks of using parallel/multi-process mode +- Document restriction that pg_bulkload supports only tables of "heap" access method +* Mon Jan 21 2019 - Moon Insung 3.1.15-1 +- Fixed pg_bulkload to mitigate attacks described in CVE-2018-1058 +- Update to pg_bulkload 3.1.15 +* Thu Nov 02 2017 - Moon Insung 3.1.14-1 +- Support PostgreSQL 10 +- Update to pg_bulkload 3.1.14 diff --git a/SPECS/pg_bulkload-pg11.spec b/SPECS/pg_bulkload-pg11.spec index a8fb184..5680a82 100644 --- a/SPECS/pg_bulkload-pg11.spec +++ b/SPECS/pg_bulkload-pg11.spec @@ -1,113 +1,113 @@ -# SPEC file for pg_bulkload on PostgreSQL 11 -# Copyright (C) 2009-2021 NIPPON TELEGRAPH AND TELEPHONE CORPORATION - -%define sname pg_bulkload -%define pgmajorversion 11 - -%define _prefix /usr/pgsql-%{pgmajorversion} -%define _libdir %{_prefix}/lib -%define _bcdir %{_libdir}/bitcode/pg_bulkload - -Summary: High speed data load utility for PostgreSQL -Name: %{sname} -Version: 3.1.18 -Release: 1%{?dist} -License: BSD -Group: Applications/Databases -# You can get the tarball by following: https://github.com/ossc-db/pg_bulkload/archive/%{version}.tar.gz -Source0: %{sname}-%{version}.tar.gz -URL: http://ossc-db.github.io/pg_bulkload/index.html -BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-%(%{__id_u} -n) - -BuildRequires: postgresql11-devel, postgresql11 -Requires: postgresql11 - - -%description -pg_bulkload provides high-speed data loading capability to PostgreSQL users. - -When we load huge amount of data to a database, it is common situation that data set to be loaded is valid and consistent. For example, dedicated tools are used to prepare such data, providing data validation in advance. In such cases, we'd like to bypass any overheads within database system to load data as quickly as possible. pg_bulkload is developed to help such situations. Therefore, it is not pg_bulkload's goal to provide detailed data validation. Rather, pg_bulkload asumes that loaded data set is validated by separate means. If you're not in such situation, you should use COPY command in PostgreSQL. - - -%package llvmjit -Requires: postgresql11-server, postgresql11-llvmjit -Requires: pg_bulkload = 3.1.18 -Summary: Just-in-time compilation support for pg_bulkload - -%description llvmjit -Just-in-time compilation support for pg_bulkdload - -%prep -rm -rf %{_libdir}/pgxs/src/backend/ - -%setup -n %{sname}-%{version} - -%build -USE_PGXS=1 make %{?_smp_mflags} MAJORVERSION=%{pgmajorversion} - -%install -%define pg_contribdir %{_datadir}/contrib -%define pg_extensiondir %{_datadir}/extension - -rm -rf %{buildroot} - -install -d %{buildroot}%{_bindir} -install -d %{buildroot}%{_libdir} -install -d %{buildroot}%{pg_contribdir} -install -d %{buildroot}%{pg_extensiondir} -install -d %{buildroot}%{_bcdir} - -install -m 755 bin/pg_bulkload %{buildroot}%{_bindir}/pg_bulkload -install -m 755 bin/postgresql %{buildroot}%{_bindir}/postgresql -install -m 755 lib/pg_bulkload.so %{buildroot}%{_libdir}/pg_bulkload.so -install -m 644 lib/pg_bulkload.bc %{buildroot}%{_bcdir}/pg_bulkload.bc - -install -m 644 lib/pg_bulkload.sql %{buildroot}%{pg_contribdir}/pg_bulkload.sql -install -m 644 lib/uninstall_pg_bulkload.sql %{buildroot}%{pg_contribdir}/uninstall_pg_bulkload.sql -install -m 644 lib/pg_bulkload.control %{buildroot}%{pg_extensiondir}/pg_bulkload.control -install -m 644 lib/pg_bulkload--1.0.sql %{buildroot}%{pg_extensiondir}/pg_bulkload--1.0.sql -install -m 644 lib/pg_bulkload--unpackaged--1.0.sql %{buildroot}%{pg_extensiondir}/pg_bulkload--unpackaged--1.0.sql - -# sample_*.ctl files are needed for rpm users. -# %{sname}-%{version} is the same path with "%setup -n"'s argument. -install -m 644 docs/sample_bin.ctl %{buildroot}%{pg_contribdir}/sample_bin.ctl -install -m 644 docs/sample_csv.ctl %{buildroot}%{pg_contribdir}/sample_csv.ctl - -%files -%defattr(755,root,root,755) -%{_bindir}/pg_bulkload -%{_bindir}/postgresql -%{_libdir}/pg_bulkload.so -%defattr(644,root,root,755) -#%doc README.pg_bulkload -%{pg_contribdir}/pg_bulkload.sql -%{pg_contribdir}/uninstall_pg_bulkload.sql -%{pg_contribdir}/sample_bin.ctl -%{pg_contribdir}/sample_csv.ctl -%{pg_extensiondir}/pg_bulkload.control -%{pg_extensiondir}/pg_bulkload--1.0.sql -%{pg_extensiondir}/pg_bulkload--unpackaged--1.0.sql - -%files llvmjit -%defattr(0755,root,root) -%{_bcdir} -%defattr(0644,root,root) -%{_bcdir}/pg_bulkload.bc - -%clean -rm -rf %{buildroot} -rm -rf %{_libdir}/pgxs/src/backend/ - -%changelog -* Tue June 01 2021 - Yanmei Sun 3.1.18-1 -- Update to pg_bulkload 3.1.18 -* Fri Feb 05 2021 - Moon Insung 3.1.17-1 -- Update to pg_bulkload 3.1.17 -* Wed Jan 22 2020 - Moon Insung 3.1.16-1 -- Update to pg_bulkload 3.1.16 -- Warn users of some risks of using parallel/multi-process mode -- Document restriction that pg_bulkload supports only tables of "heap" access method -* Mon Jan 21 2019 - Moon Insung 3.1.15-1 -- Fixed pg_bulkload to mitigate attacks described in CVE-2018-1058 -- Added llvm.rpm for pg_bulkload to support llvmjit of PostgreSQL -- Update to pg_bulkload 3.1.15 +# SPEC file for pg_bulkload on PostgreSQL 11 +# Copyright (C) 2009-2021 NIPPON TELEGRAPH AND TELEPHONE CORPORATION + +%define sname pg_bulkload +%define pgmajorversion 11 + +%define _prefix /usr/pgsql-%{pgmajorversion} +%define _libdir %{_prefix}/lib +%define _bcdir %{_libdir}/bitcode/pg_bulkload + +Summary: High speed data load utility for PostgreSQL +Name: %{sname} +Version: 3.1.18 +Release: 1%{?dist} +License: BSD +Group: Applications/Databases +# You can get the tarball by following: https://github.com/ossc-db/pg_bulkload/archive/%{version}.tar.gz +Source0: %{sname}-%{version}.tar.gz +URL: http://ossc-db.github.io/pg_bulkload/index.html +BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-%(%{__id_u} -n) + +BuildRequires: postgresql11-devel, postgresql11 +Requires: postgresql11 + + +%description +pg_bulkload provides high-speed data loading capability to PostgreSQL users. + +When we load huge amount of data to a database, it is common situation that data set to be loaded is valid and consistent. For example, dedicated tools are used to prepare such data, providing data validation in advance. In such cases, we'd like to bypass any overheads within database system to load data as quickly as possible. pg_bulkload is developed to help such situations. Therefore, it is not pg_bulkload's goal to provide detailed data validation. Rather, pg_bulkload asumes that loaded data set is validated by separate means. If you're not in such situation, you should use COPY command in PostgreSQL. + + +%package llvmjit +Requires: postgresql11-server, postgresql11-llvmjit +Requires: pg_bulkload = 3.1.18 +Summary: Just-in-time compilation support for pg_bulkload + +%description llvmjit +Just-in-time compilation support for pg_bulkdload + +%prep +rm -rf %{_libdir}/pgxs/src/backend/ + +%setup -n %{sname}-%{version} + +%build +USE_PGXS=1 make %{?_smp_mflags} MAJORVERSION=%{pgmajorversion} + +%install +%define pg_contribdir %{_datadir}/contrib +%define pg_extensiondir %{_datadir}/extension + +rm -rf %{buildroot} + +install -d %{buildroot}%{_bindir} +install -d %{buildroot}%{_libdir} +install -d %{buildroot}%{pg_contribdir} +install -d %{buildroot}%{pg_extensiondir} +install -d %{buildroot}%{_bcdir} + +install -m 755 bin/pg_bulkload %{buildroot}%{_bindir}/pg_bulkload +install -m 755 bin/postgresql %{buildroot}%{_bindir}/postgresql +install -m 755 lib/pg_bulkload.so %{buildroot}%{_libdir}/pg_bulkload.so +install -m 644 lib/pg_bulkload.bc %{buildroot}%{_bcdir}/pg_bulkload.bc + +install -m 644 lib/pg_bulkload.sql %{buildroot}%{pg_contribdir}/pg_bulkload.sql +install -m 644 lib/uninstall_pg_bulkload.sql %{buildroot}%{pg_contribdir}/uninstall_pg_bulkload.sql +install -m 644 lib/pg_bulkload.control %{buildroot}%{pg_extensiondir}/pg_bulkload.control +install -m 644 lib/pg_bulkload--1.0.sql %{buildroot}%{pg_extensiondir}/pg_bulkload--1.0.sql +install -m 644 lib/pg_bulkload--unpackaged--1.0.sql %{buildroot}%{pg_extensiondir}/pg_bulkload--unpackaged--1.0.sql + +# sample_*.ctl files are needed for rpm users. +# %{sname}-%{version} is the same path with "%setup -n"'s argument. +install -m 644 docs/sample_bin.ctl %{buildroot}%{pg_contribdir}/sample_bin.ctl +install -m 644 docs/sample_csv.ctl %{buildroot}%{pg_contribdir}/sample_csv.ctl + +%files +%defattr(755,root,root,755) +%{_bindir}/pg_bulkload +%{_bindir}/postgresql +%{_libdir}/pg_bulkload.so +%defattr(644,root,root,755) +#%doc README.pg_bulkload +%{pg_contribdir}/pg_bulkload.sql +%{pg_contribdir}/uninstall_pg_bulkload.sql +%{pg_contribdir}/sample_bin.ctl +%{pg_contribdir}/sample_csv.ctl +%{pg_extensiondir}/pg_bulkload.control +%{pg_extensiondir}/pg_bulkload--1.0.sql +%{pg_extensiondir}/pg_bulkload--unpackaged--1.0.sql + +%files llvmjit +%defattr(0755,root,root) +%{_bcdir} +%defattr(0644,root,root) +%{_bcdir}/pg_bulkload.bc + +%clean +rm -rf %{buildroot} +rm -rf %{_libdir}/pgxs/src/backend/ + +%changelog +* Tue Jun 01 2021 - Yanmei Sun 3.1.18-1 +- Update to pg_bulkload 3.1.18 +* Fri Feb 05 2021 - Moon Insung 3.1.17-1 +- Update to pg_bulkload 3.1.17 +* Wed Jan 22 2020 - Moon Insung 3.1.16-1 +- Update to pg_bulkload 3.1.16 +- Warn users of some risks of using parallel/multi-process mode +- Document restriction that pg_bulkload supports only tables of "heap" access method +* Mon Jan 21 2019 - Moon Insung 3.1.15-1 +- Fixed pg_bulkload to mitigate attacks described in CVE-2018-1058 +- Added llvm.rpm for pg_bulkload to support llvmjit of PostgreSQL +- Update to pg_bulkload 3.1.15 diff --git a/SPECS/pg_bulkload-pg12.sepc b/SPECS/pg_bulkload-pg12.spec similarity index 96% rename from SPECS/pg_bulkload-pg12.sepc rename to SPECS/pg_bulkload-pg12.spec index 75e0707..abfe659 100644 --- a/SPECS/pg_bulkload-pg12.sepc +++ b/SPECS/pg_bulkload-pg12.spec @@ -1,109 +1,109 @@ -# SPEC file for pg_bulkload on PostgreSQL 12 -# Copyright (C) 2009-2021 NIPPON TELEGRAPH AND TELEPHONE CORPORATION - -%define sname pg_bulkload -%define pgmajorversion 12 - -%define _prefix /usr/pgsql-%{pgmajorversion} -%define _libdir %{_prefix}/lib -%define _bcdir %{_libdir}/bitcode/pg_bulkload - -Summary: High speed data load utility for PostgreSQL -Name: %{sname} -Version: 3.1.18 -Release: 1%{?dist} -License: BSD -Group: Applications/Databases -# You can get the tarball by following: https://github.com/ossc-db/pg_bulkload/archive/%{version}.tar.gz -Source0: %{sname}-%{version}.tar.gz -URL: http://ossc-db.github.io/pg_bulkload/index.html -BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-%(%{__id_u} -n) - -BuildRequires: postgresql12-devel, postgresql12 -Requires: postgresql12 - - -%description -pg_bulkload provides high-speed data loading capability to PostgreSQL users. - -When we load huge amount of data to a database, it is common situation that data set to be loaded is valid and consistent. For example, dedicated tools are used to prepare such data, providing data validation in advance. In such cases, we'd like to bypass any overheads within database system to load data as quickly as possible. pg_bulkload is developed to help such situations. Therefore, it is not pg_bulkload's goal to provide detailed data validation. Rather, pg_bulkload asumes that loaded data set is validated by separate means. If you're not in such situation, you should use COPY command in PostgreSQL. - - -%package llvmjit -Requires: postgresql12-server, postgresql12-llvmjit -Requires: pg_bulkload = 3.1.18 -Summary: Just-in-time compilation support for pg_bulkload - -%description llvmjit -Just-in-time compilation support for pg_bulkdload - -%prep -rm -rf %{_libdir}/pgxs/src/backend/ - -%setup -n %{sname}-%{version} - -%build -USE_PGXS=1 make %{?_smp_mflags} MAJORVERSION=%{pgmajorversion} - -%install -%define pg_contribdir %{_datadir}/contrib -%define pg_extensiondir %{_datadir}/extension - -rm -rf %{buildroot} - -install -d %{buildroot}%{_bindir} -install -d %{buildroot}%{_libdir} -install -d %{buildroot}%{pg_contribdir} -install -d %{buildroot}%{pg_extensiondir} -install -d %{buildroot}%{_bcdir} - -install -m 755 bin/pg_bulkload %{buildroot}%{_bindir}/pg_bulkload -install -m 755 bin/postgresql %{buildroot}%{_bindir}/postgresql -install -m 755 lib/pg_bulkload.so %{buildroot}%{_libdir}/pg_bulkload.so -install -m 644 lib/pg_bulkload.bc %{buildroot}%{_bcdir}/pg_bulkload.bc - -install -m 644 lib/pg_bulkload.sql %{buildroot}%{pg_contribdir}/pg_bulkload.sql -install -m 644 lib/uninstall_pg_bulkload.sql %{buildroot}%{pg_contribdir}/uninstall_pg_bulkload.sql -install -m 644 lib/pg_bulkload.control %{buildroot}%{pg_extensiondir}/pg_bulkload.control -install -m 644 lib/pg_bulkload--1.0.sql %{buildroot}%{pg_extensiondir}/pg_bulkload--1.0.sql -install -m 644 lib/pg_bulkload--unpackaged--1.0.sql %{buildroot}%{pg_extensiondir}/pg_bulkload--unpackaged--1.0.sql - -# sample_*.ctl files are needed for rpm users. -# %{sname}-%{version} is the same path with "%setup -n"'s argument. -install -m 644 docs/sample_bin.ctl %{buildroot}%{pg_contribdir}/sample_bin.ctl -install -m 644 docs/sample_csv.ctl %{buildroot}%{pg_contribdir}/sample_csv.ctl - -%files -%defattr(755,root,root,755) -%{_bindir}/pg_bulkload -%{_bindir}/postgresql -%{_libdir}/pg_bulkload.so -%defattr(644,root,root,755) -#%doc README.pg_bulkload -%{pg_contribdir}/pg_bulkload.sql -%{pg_contribdir}/uninstall_pg_bulkload.sql -%{pg_contribdir}/sample_bin.ctl -%{pg_contribdir}/sample_csv.ctl -%{pg_extensiondir}/pg_bulkload.control -%{pg_extensiondir}/pg_bulkload--1.0.sql -%{pg_extensiondir}/pg_bulkload--unpackaged--1.0.sql - -%files llvmjit -%defattr(0755,root,root) -%{_bcdir} -%defattr(0644,root,root) -%{_bcdir}/pg_bulkload.bc - -%clean -rm -rf %{buildroot} -rm -rf %{_libdir}/pgxs/src/backend/ - -%changelog -* Tue June 01 2021 - Yanmei Sun 3.1.18-1 -- Update to pg_bulkload 3.1.18 -* Fri Feb 05 2021 - Moon Insung 3.1.17-1 -- Update to pg_bulkload 3.1.17 -* Wed Jan 22 2020 - Moon Insung 3.1.16-1 -- Update to pg_bulkload 3.1.16 -- Warn users of some risks of using parallel/multi-process mode -- Document restriction that pg_bulkload supports only tables of "heap" access method +# SPEC file for pg_bulkload on PostgreSQL 12 +# Copyright (C) 2009-2021 NIPPON TELEGRAPH AND TELEPHONE CORPORATION + +%define sname pg_bulkload +%define pgmajorversion 12 + +%define _prefix /usr/pgsql-%{pgmajorversion} +%define _libdir %{_prefix}/lib +%define _bcdir %{_libdir}/bitcode/pg_bulkload + +Summary: High speed data load utility for PostgreSQL +Name: %{sname} +Version: 3.1.18 +Release: 1%{?dist} +License: BSD +Group: Applications/Databases +# You can get the tarball by following: https://github.com/ossc-db/pg_bulkload/archive/%{version}.tar.gz +Source0: %{sname}-%{version}.tar.gz +URL: http://ossc-db.github.io/pg_bulkload/index.html +BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-%(%{__id_u} -n) + +BuildRequires: postgresql12-devel, postgresql12 +Requires: postgresql12 + + +%description +pg_bulkload provides high-speed data loading capability to PostgreSQL users. + +When we load huge amount of data to a database, it is common situation that data set to be loaded is valid and consistent. For example, dedicated tools are used to prepare such data, providing data validation in advance. In such cases, we'd like to bypass any overheads within database system to load data as quickly as possible. pg_bulkload is developed to help such situations. Therefore, it is not pg_bulkload's goal to provide detailed data validation. Rather, pg_bulkload asumes that loaded data set is validated by separate means. If you're not in such situation, you should use COPY command in PostgreSQL. + + +%package llvmjit +Requires: postgresql12-server, postgresql12-llvmjit +Requires: pg_bulkload = 3.1.18 +Summary: Just-in-time compilation support for pg_bulkload + +%description llvmjit +Just-in-time compilation support for pg_bulkdload + +%prep +rm -rf %{_libdir}/pgxs/src/backend/ + +%setup -n %{sname}-%{version} + +%build +USE_PGXS=1 make %{?_smp_mflags} MAJORVERSION=%{pgmajorversion} + +%install +%define pg_contribdir %{_datadir}/contrib +%define pg_extensiondir %{_datadir}/extension + +rm -rf %{buildroot} + +install -d %{buildroot}%{_bindir} +install -d %{buildroot}%{_libdir} +install -d %{buildroot}%{pg_contribdir} +install -d %{buildroot}%{pg_extensiondir} +install -d %{buildroot}%{_bcdir} + +install -m 755 bin/pg_bulkload %{buildroot}%{_bindir}/pg_bulkload +install -m 755 bin/postgresql %{buildroot}%{_bindir}/postgresql +install -m 755 lib/pg_bulkload.so %{buildroot}%{_libdir}/pg_bulkload.so +install -m 644 lib/pg_bulkload.bc %{buildroot}%{_bcdir}/pg_bulkload.bc + +install -m 644 lib/pg_bulkload.sql %{buildroot}%{pg_contribdir}/pg_bulkload.sql +install -m 644 lib/uninstall_pg_bulkload.sql %{buildroot}%{pg_contribdir}/uninstall_pg_bulkload.sql +install -m 644 lib/pg_bulkload.control %{buildroot}%{pg_extensiondir}/pg_bulkload.control +install -m 644 lib/pg_bulkload--1.0.sql %{buildroot}%{pg_extensiondir}/pg_bulkload--1.0.sql +install -m 644 lib/pg_bulkload--unpackaged--1.0.sql %{buildroot}%{pg_extensiondir}/pg_bulkload--unpackaged--1.0.sql + +# sample_*.ctl files are needed for rpm users. +# %{sname}-%{version} is the same path with "%setup -n"'s argument. +install -m 644 docs/sample_bin.ctl %{buildroot}%{pg_contribdir}/sample_bin.ctl +install -m 644 docs/sample_csv.ctl %{buildroot}%{pg_contribdir}/sample_csv.ctl + +%files +%defattr(755,root,root,755) +%{_bindir}/pg_bulkload +%{_bindir}/postgresql +%{_libdir}/pg_bulkload.so +%defattr(644,root,root,755) +#%doc README.pg_bulkload +%{pg_contribdir}/pg_bulkload.sql +%{pg_contribdir}/uninstall_pg_bulkload.sql +%{pg_contribdir}/sample_bin.ctl +%{pg_contribdir}/sample_csv.ctl +%{pg_extensiondir}/pg_bulkload.control +%{pg_extensiondir}/pg_bulkload--1.0.sql +%{pg_extensiondir}/pg_bulkload--unpackaged--1.0.sql + +%files llvmjit +%defattr(0755,root,root) +%{_bcdir} +%defattr(0644,root,root) +%{_bcdir}/pg_bulkload.bc + +%clean +rm -rf %{buildroot} +rm -rf %{_libdir}/pgxs/src/backend/ + +%changelog +* Tue Jun 01 2021 - Yanmei Sun 3.1.18-1 +- Update to pg_bulkload 3.1.18 +* Fri Feb 05 2021 - Moon Insung 3.1.17-1 +- Update to pg_bulkload 3.1.17 +* Wed Jan 22 2020 - Moon Insung 3.1.16-1 +- Update to pg_bulkload 3.1.16 +- Warn users of some risks of using parallel/multi-process mode +- Document restriction that pg_bulkload supports only tables of "heap" access method diff --git a/SPECS/pg_bulkload-pg13.spec b/SPECS/pg_bulkload-pg13.spec index 133cd03..8fb36be 100755 --- a/SPECS/pg_bulkload-pg13.spec +++ b/SPECS/pg_bulkload-pg13.spec @@ -99,7 +99,7 @@ rm -rf %{buildroot} rm -rf %{_libdir}/pgxs/src/backend/ %changelog -* Tue June 01 2021 - Yanmei Sun 3.1.18-1 +* Tue Jun 01 2021 - Yanmei Sun 3.1.18-1 - Update to pg_bulkload 3.1.18 * Fri Feb 05 2021 - Moon Insung 3.1.17-1 - Update to pg_bulkload 3.1.17 diff --git a/SPECS/pg_bulkload-pg96.spec b/SPECS/pg_bulkload-pg96.spec index 50e99a4..fb91653 100644 --- a/SPECS/pg_bulkload-pg96.spec +++ b/SPECS/pg_bulkload-pg96.spec @@ -1,111 +1,111 @@ -# SPEC file for pg_bulkload on PostgreSQL 9.6 -# Copyright (C) 2009-2021 NIPPON TELEGRAPH AND TELEPHONE CORPORATION - -%define sname pg_bulkload -%define pgmajorversion 9.6 - -%define _prefix /usr/pgsql-%{pgmajorversion} -%define _libdir %{_prefix}/lib - -Summary: High speed data load utility for PostgreSQL -Name: %{sname} -Version: 3.1.18 -Release: 1%{?dist} -License: BSD -Group: Applications/Databases -# You can get the tarball by following: https://github.com/ossc-db/pg_bulkload/archive/%{version}.tar.gz -Source0: %{sname}-%{version}.tar.gz -URL: http://ossc-db.github.io/pg_bulkload/index.html -BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-%(%{__id_u} -n) - -BuildRequires: postgresql96-devel, postgresql96 -Requires: postgresql96 - - -%description -pg_bulkload provides high-speed data loading capability to PostgreSQL users. - -When we load huge amount of data to a database, it is common situation that data set to be loaded is valid and consistent. For example, dedicated tools are used to prepare such data, providing data validation in advance. In such cases, we'd like to bypass any overheads within database system to load data as quickly as possible. pg_bulkload is developed to help such situations. Therefore, it is not pg_bulkload's goal to provide detailed data validation. Rather, pg_bulkload asumes that loaded data set is validated by separate means. If you're not in such situation, you should use COPY command in PostgreSQL. - - -%prep -rm -rf %{_libdir}/pgxs/src/backend/ - -%setup -n %{sname}-%{version} - -%build -USE_PGXS=1 make %{?_smp_mflags} MAJORVERSION=%{pgmajorversion} - -%install -%define pg_contribdir %{_datadir}/contrib -%define pg_extensiondir %{_datadir}/extension - -rm -rf %{buildroot} - -install -d %{buildroot}%{_bindir} -install -d %{buildroot}%{_libdir} -install -d %{buildroot}%{pg_contribdir} -install -d %{buildroot}%{pg_extensiondir} - -install -m 755 bin/pg_bulkload %{buildroot}%{_bindir}/pg_bulkload -install -m 755 bin/postgresql %{buildroot}%{_bindir}/postgresql -install -m 755 lib/pg_bulkload.so %{buildroot}%{_libdir}/pg_bulkload.so - -install -m 644 lib/pg_bulkload.sql %{buildroot}%{pg_contribdir}/pg_bulkload.sql -install -m 644 lib/uninstall_pg_bulkload.sql %{buildroot}%{pg_contribdir}/uninstall_pg_bulkload.sql -install -m 644 lib/pg_bulkload.control %{buildroot}%{pg_extensiondir}/pg_bulkload.control -install -m 644 lib/pg_bulkload--1.0.sql %{buildroot}%{pg_extensiondir}/pg_bulkload--1.0.sql -install -m 644 lib/pg_bulkload--unpackaged--1.0.sql %{buildroot}%{pg_extensiondir}/pg_bulkload--unpackaged--1.0.sql - -# sample_*.ctl files are needed for rpm users. -# %{sname}-%{version} is the same path with "%setup -n"'s argument. -install -m 644 docs/sample_bin.ctl %{buildroot}%{pg_contribdir}/sample_bin.ctl -install -m 644 docs/sample_csv.ctl %{buildroot}%{pg_contribdir}/sample_csv.ctl - -%files -%defattr(755,root,root,755) -%{_bindir}/pg_bulkload -%{_bindir}/postgresql -%{_libdir}/pg_bulkload.so -%defattr(644,root,root,755) -#%doc README.pg_bulkload -%{pg_contribdir}/pg_bulkload.sql -%{pg_contribdir}/uninstall_pg_bulkload.sql -%{pg_contribdir}/sample_bin.ctl -%{pg_contribdir}/sample_csv.ctl -%{pg_extensiondir}/pg_bulkload.control -%{pg_extensiondir}/pg_bulkload--1.0.sql -%{pg_extensiondir}/pg_bulkload--unpackaged--1.0.sql - -%clean -rm -rf %{buildroot} -rm -rf %{_libdir}/pgxs/src/backend/ - -%changelog -* Tue June 01 2021 - Yanmei Sun 3.1.18-1 -- Update to pg_bulkload 3.1.18 -* Fri Feb 05 2021 - Moon Insung 3.1.17-1 -- Update to pg_bulkload 3.1.17 -* Wed Jan 22 2020 - Moon Insung 3.1.16-1 -- Update to pg_bulkload 3.1.16 -- Warn users of some risks of using parallel/multi-process mode -- Document restriction that pg_bulkload supports only tables of "heap" access method -* Mon Jan 21 2019 - Moon Insung 3.1.15-1 -- Fixed pg_bulkload to mitigate attacks described in CVE-2018-1058 -- Update to pg_bulkload 3.1.15 -* Thu Nov 02 2017 - Moon Insung 3.1.14-1 -- Support PostgreSQL 10 -- Update to pg_bulkload 3.1.14 -* Mon Jan 27 2017 - Atsushi Torikoshi 3.1.13-1 -- Fixed crash when using MULTI_PROCESS mode with input file containing a malformed record -- Prevented CSVParserRead() from requesting too much memory causing error eventually -- Update to pg_bulkload 3.1.13 -* Mon Nov 16 2016 - Atsushi Torikoshi 3.1.12-1 -- Update version number and fix regression test expected output -- Update to pg_bulkload 3.1.12 -* Mon Nov 11 2016 - Atsushi Torikoshi 3.1.11-1 -- Fixed a bug in block number calculation in direct write mode -- Update to pg_bulkload 3.1.11 -* Mon Sep 29 2016 - Masanori Ooyama 3.1.10-1 -- Support PostgreSQL 9.6 -- Update to pg_bulkload 3.1.10 +# SPEC file for pg_bulkload on PostgreSQL 9.6 +# Copyright (C) 2009-2021 NIPPON TELEGRAPH AND TELEPHONE CORPORATION + +%define sname pg_bulkload +%define pgmajorversion 9.6 + +%define _prefix /usr/pgsql-%{pgmajorversion} +%define _libdir %{_prefix}/lib + +Summary: High speed data load utility for PostgreSQL +Name: %{sname} +Version: 3.1.18 +Release: 1%{?dist} +License: BSD +Group: Applications/Databases +# You can get the tarball by following: https://github.com/ossc-db/pg_bulkload/archive/%{version}.tar.gz +Source0: %{sname}-%{version}.tar.gz +URL: http://ossc-db.github.io/pg_bulkload/index.html +BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-%(%{__id_u} -n) + +BuildRequires: postgresql96-devel, postgresql96 +Requires: postgresql96 + + +%description +pg_bulkload provides high-speed data loading capability to PostgreSQL users. + +When we load huge amount of data to a database, it is common situation that data set to be loaded is valid and consistent. For example, dedicated tools are used to prepare such data, providing data validation in advance. In such cases, we'd like to bypass any overheads within database system to load data as quickly as possible. pg_bulkload is developed to help such situations. Therefore, it is not pg_bulkload's goal to provide detailed data validation. Rather, pg_bulkload asumes that loaded data set is validated by separate means. If you're not in such situation, you should use COPY command in PostgreSQL. + + +%prep +rm -rf %{_libdir}/pgxs/src/backend/ + +%setup -n %{sname}-%{version} + +%build +USE_PGXS=1 make %{?_smp_mflags} MAJORVERSION=%{pgmajorversion} + +%install +%define pg_contribdir %{_datadir}/contrib +%define pg_extensiondir %{_datadir}/extension + +rm -rf %{buildroot} + +install -d %{buildroot}%{_bindir} +install -d %{buildroot}%{_libdir} +install -d %{buildroot}%{pg_contribdir} +install -d %{buildroot}%{pg_extensiondir} + +install -m 755 bin/pg_bulkload %{buildroot}%{_bindir}/pg_bulkload +install -m 755 bin/postgresql %{buildroot}%{_bindir}/postgresql +install -m 755 lib/pg_bulkload.so %{buildroot}%{_libdir}/pg_bulkload.so + +install -m 644 lib/pg_bulkload.sql %{buildroot}%{pg_contribdir}/pg_bulkload.sql +install -m 644 lib/uninstall_pg_bulkload.sql %{buildroot}%{pg_contribdir}/uninstall_pg_bulkload.sql +install -m 644 lib/pg_bulkload.control %{buildroot}%{pg_extensiondir}/pg_bulkload.control +install -m 644 lib/pg_bulkload--1.0.sql %{buildroot}%{pg_extensiondir}/pg_bulkload--1.0.sql +install -m 644 lib/pg_bulkload--unpackaged--1.0.sql %{buildroot}%{pg_extensiondir}/pg_bulkload--unpackaged--1.0.sql + +# sample_*.ctl files are needed for rpm users. +# %{sname}-%{version} is the same path with "%setup -n"'s argument. +install -m 644 docs/sample_bin.ctl %{buildroot}%{pg_contribdir}/sample_bin.ctl +install -m 644 docs/sample_csv.ctl %{buildroot}%{pg_contribdir}/sample_csv.ctl + +%files +%defattr(755,root,root,755) +%{_bindir}/pg_bulkload +%{_bindir}/postgresql +%{_libdir}/pg_bulkload.so +%defattr(644,root,root,755) +#%doc README.pg_bulkload +%{pg_contribdir}/pg_bulkload.sql +%{pg_contribdir}/uninstall_pg_bulkload.sql +%{pg_contribdir}/sample_bin.ctl +%{pg_contribdir}/sample_csv.ctl +%{pg_extensiondir}/pg_bulkload.control +%{pg_extensiondir}/pg_bulkload--1.0.sql +%{pg_extensiondir}/pg_bulkload--unpackaged--1.0.sql + +%clean +rm -rf %{buildroot} +rm -rf %{_libdir}/pgxs/src/backend/ + +%changelog +* Tue Jun 01 2021 - Yanmei Sun 3.1.18-1 +- Update to pg_bulkload 3.1.18 +* Fri Feb 05 2021 - Moon Insung 3.1.17-1 +- Update to pg_bulkload 3.1.17 +* Wed Jan 22 2020 - Moon Insung 3.1.16-1 +- Update to pg_bulkload 3.1.16 +- Warn users of some risks of using parallel/multi-process mode +- Document restriction that pg_bulkload supports only tables of "heap" access method +* Mon Jan 21 2019 - Moon Insung 3.1.15-1 +- Fixed pg_bulkload to mitigate attacks described in CVE-2018-1058 +- Update to pg_bulkload 3.1.15 +* Thu Nov 02 2017 - Moon Insung 3.1.14-1 +- Support PostgreSQL 10 +- Update to pg_bulkload 3.1.14 +* Mon Jan 27 2017 - Atsushi Torikoshi 3.1.13-1 +- Fixed crash when using MULTI_PROCESS mode with input file containing a malformed record +- Prevented CSVParserRead() from requesting too much memory causing error eventually +- Update to pg_bulkload 3.1.13 +* Mon Nov 16 2016 - Atsushi Torikoshi 3.1.12-1 +- Update version number and fix regression test expected output +- Update to pg_bulkload 3.1.12 +* Mon Nov 11 2016 - Atsushi Torikoshi 3.1.11-1 +- Fixed a bug in block number calculation in direct write mode +- Update to pg_bulkload 3.1.11 +* Mon Sep 29 2016 - Masanori Ooyama 3.1.10-1 +- Support PostgreSQL 9.6 +- Update to pg_bulkload 3.1.10