1Reporting Bugs
2==============
3
4pgloader is a software and as such contains bugs. Most bugs are easy to
5solve and taken care of in a short delay. For this to be possible though,
6bug reports need to follow those recommandations:
7
8  - include pgloader version,
9  - include problematic input and output,
10  - include a description of the output you expected,
11  - explain the difference between the ouput you have and the one you expected,
12  - include a self-reproducing test-case
13
14Test Cases to Reproduce Bugs
15----------------------------
16
17Use the *inline* source type to help reproduce a bug, as in the pgloader tests::
18
19  LOAD CSV
20     FROM INLINE
21     INTO postgresql://dim@localhost/pgloader?public."HS"
22
23     WITH truncate,
24          fields terminated by '\t',
25          fields not enclosed,
26          fields escaped by backslash-quote,
27          quote identifiers
28
29      SET work_mem to '128MB',
30          standard_conforming_strings to 'on',
31          application_name to 'my app name'
32
33   BEFORE LOAD DO
34    $$ create extension if not exists hstore; $$,
35    $$ drop table if exists "HS"; $$,
36    $$ CREATE TABLE "HS"
37       (
38          id     serial primary key,
39          kv     hstore
40       )
41    $$;
42
43
44  1	email=>foo@example.com,a=>b
45  2	test=>value
46  3	a=>b,c=>"quoted hstore value",d=>other
47  4	baddata
48
49
50