TODO update with status, preparing a debian experimental release

This commit is contained in:
dim 2008-02-25 16:27:07 +00:00
parent ca2ba09c6a
commit a018ddac95
3 changed files with 38 additions and 5 deletions

View File

@ -1,4 +1,4 @@
# $Id: Makefile,v 1.14 2008-02-25 15:47:18 dim Exp $
# $Id: Makefile,v 1.15 2008-02-25 16:27:06 dim Exp $
#
# Makefile for debian packaging purpose, make install not intended to work.
@ -59,7 +59,7 @@ deb:
mkdir -p $(DEBDIR)/pgloader-$(VERSION)
mkdir -p $(EXPORT)
cp -a . $(EXPORT)
for n in ".#*" "*~" "*.pyc" "build-stamp" "configure-stamp"; do \
for n in ".#*" "*~" "*.pyc" "build-stamp" "configure-stamp" "parallel.[^d]" ; do \
find $(EXPORT) -name "$$n" -print0|xargs -0 echo rm -f; \
find $(EXPORT) -name "$$n" -print0|xargs -0 rm -f; \
done

View File

@ -2,12 +2,34 @@
== Multi Threaded Import ==
* Terminate +split_file_reading+ behavior implementation (status: debug)
Release-Canditate status now. See documentation and its new +PARALLEL
LOADING+ section. Supports for both round-robin reader and split file
reading concepts, and provides processing multiple sections at a
time. Please test if you're interrested.
* Implement 'round robin reader' behavior
Current status::
Wait for user complaints, get a version at
http://pgloader.projects.postgresql.org/dev/[].
Limits::
See http://docs.python.org/api/threads.html[], and consider
+pgloader+ is using generators, so maybe the problem won't get so
huga as to completely inhibit any performance benefit from
multi-threaded processing.
Version::
+2.3.0+, currently in +~dev2+, which could be read 'Release Candidate'.
== Constraint Exclusion support ==
Current status::
Design seems ok enough for devel to get started anytime. Will wait
for +2.3.0+ to get released.
Version::
Targeted for +2.4.0+, which will certainly be the next one after
+2.3.0+ gets released.
=== User level configuration
At user level, you will have to add a +constraint_exclusion = on+
@ -106,6 +128,13 @@ stop/start Threads at each new line.
== Reject Behaviour ==
Current status::
In need for design.
Version::
After +2.4.0+, either as a minor version or a +2.5.0+ one,
depending on the author mood...
Implement several reject behaviours for pgloader and allow users to
configure them depending on the error we had. For example user might
configure pgloader to load rejected data to some other table when the
@ -113,6 +142,10 @@ error is PK violation.
== Fixed Format ==
Current status::
Designs easy and ok, needs to get done sometime, in a minor release
between 'big items'
Support fixed format: no separator, known length (in bytes) per
column.

2
debian/changelog vendored
View File

@ -1,4 +1,4 @@
pgloader (2.3.0~dev2-1) unstable; urgency=low
pgloader (2.3.0~dev2-1) experimental; urgency=low
* columns = * is now supported