mirror of
https://github.com/dimitri/pgloader.git
synced 2025-08-06 22:37:02 +02:00
c38798a4dd
That allows using the same SQL files as usual when using pgloader, as it even supports the \i and \ir psql features (and dollar quoting, etc). In passing, refactor docs to avoid saying the same things all over the place, which isn't a very good idea in a man page, at least as far editing it is involved.
35 lines
774 B
PL/PgSQL
Vendored
35 lines
774 B
PL/PgSQL
Vendored
create extension if not exists ip4r;
|
|
|
|
create schema if not exists geolite;
|
|
|
|
create table if not exists geolite.location
|
|
(
|
|
locid integer primary key,
|
|
country text,
|
|
region text,
|
|
city text,
|
|
postalcode text,
|
|
location point,
|
|
metrocode text,
|
|
areacode text
|
|
);
|
|
|
|
create table if not exists geolite.blocks
|
|
(
|
|
iprange ip4r,
|
|
locid integer
|
|
);
|
|
|
|
create or replace function geolite.locate(ip ip4)
|
|
returns geolite.location
|
|
language sql
|
|
as $$
|
|
select l.locid, country, region, city, postalcode, location, metrocode, areacode
|
|
from geolite.location l join geolite.blocks b using(locid)
|
|
where b.iprange >>= $1;
|
|
$$;
|
|
|
|
drop index if exists geolite.blocks_ip4r_idx;
|
|
truncate table geolite.blocks, geolite.location cascade;
|
|
|