-
Notifications
You must be signed in to change notification settings - Fork 75
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
432 additions
and
432 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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 <[email protected]> 3.1.18-1 | ||
| - Update to pg_bulkload 3.1.18 | ||
| * Fri Feb 05 2021 - Moon Insung <[email protected]> 3.1.17-1 | ||
| - Update to pg_bulkload 3.1.17 | ||
| * Wed Jan 22 2020 - Moon Insung <[email protected]> 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 <[email protected]> 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 <[email protected]> 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 <[email protected]> 3.1.18-1 | ||
| - Update to pg_bulkload 3.1.18 | ||
| * Fri Feb 05 2021 - Moon Insung <[email protected]> 3.1.17-1 | ||
| - Update to pg_bulkload 3.1.17 | ||
| * Wed Jan 22 2020 - Moon Insung <[email protected]> 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 <[email protected]> 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 <[email protected]> 3.1.14-1 | ||
| - Support PostgreSQL 10 | ||
| - Update to pg_bulkload 3.1.14 |
Oops, something went wrong.