Thread: [submit code] I develop a tool for pgsql, how can I submit it

leap wrote:
> I develop a tool for pgsql, I want to submit it on pgsql.
> how can I submit it?
> 
> address: https://github.com/leapking/pgcheck

I would leave it on Github and add some documentation.

A lot of great tools for PostgreSQL are not part of the
core distribution; that doesn't mean that they are unloved.

Yours,
Laurenz Albe

2018-03-13 12:19 GMT-03:00 leap <leapking@126.com>:
> I develop a tool for pgsql, I want to submit it on pgsql.
> how can I submit it?
>
As Laurenz said a tool doesn't necessarily have to be part of
PostgreSQL. Sometimes a lot of people ask for a tool, someone write it
and the community decide to maintain it. I'm not sure this is the case
for your tool. The pro is that the tool will be maintained by a group
of experienced programmers (I'm not saying you can't have this group
outside PostgreSQL project. You may have enough interest if people are
excited by it). The con about this direction is that the tool
development cycle is tied to PostgreSQL (which means 1-year cycle and
slow development over time). Since I do a lot of debug it seems very
useful for me. If you decide to convince people about the usefulness
of your tool, you should: (i) remove some overlap between the tool and
core, (ii) cleanup your code to follow the PostgreSQL guidelines,
(iii) reuse core functions, (iv) reuse constants instead of redefine
them and (v) document everything. Steps (i), (iii) and (iv) may
require some code rearrange in PostgreSQL. Even if you decide to
continue the development outside PostgreSQL, those steps would improve
your code.


-- 
   Euler Taveira                                   Timbira -
http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento

Hello leap,

> hello!
> I develop a tool for pgsql, I want to submit it on pgsql.
> how can I submit it?
> address: https://github.com/leapking/pgcheck

It's always nice to see another great tool! Thanks a lot for sharing it.
I believe you should write a blog post about it for PostgreSQL Planet or
at least submit a link to Reddit and/or Hacker News. Also consider
submitting a talk about it to PostgreSQL conferences.

I couldn't not notice that actually it looks quite similar to
pg_filedump [1] which is currently maintained by the community. Perhaps
you would be interested in porting the part of pgcheck's functionality
that is missing in pg_filedump to pg_filedump? Or maybe vice versa? :)

Fun fact! pg_filedump is designed for reading, checking and recovering
data from database files. Since these files are usually recovered from a
backup or corrupted hard drive pg_filedump will be most likely executed
on the system which doesn't has a PostgreSQL package installed. And it's
distributed separately just for this reason I believe.

[1]: https://git.postgresql.org/gitweb/?p=pg_filedump.git;a=summary

--
Best regards,
Aleksander Alekseev

Hello leap,

> I don't know how to "submit a link to Reddit and/or Hacker News". if
> some people also like pgcheck after know pg_filedump, hope to help me
> let more people to know it.

These are sites where people involved in IT share links they find
interesting and other people vote for the links:

https://news.ycombinator.com/
https://www.reddit.com/r/PostgreSQL/

--
Best regards,
Aleksander Alekseev