Mailing list archiver

[Jordan Deitch]

This project serves to organize and archive the postgres mailing list:

http://pg.rsa.pub/

Let me know what you think, or if you have any suggestions.
I left email addresses off the site to protect privacy.

p.s: you can click messages to collapse the tree

Thanks

Re: Mailing list archiver

[Jordan Deitch]

Thanks for the feedback! I will continue to address these issues, and I
intend on adding #postgresql IRC logs as well :-)
This software was written by me particularly for this purpose; I will clean
up / comment, then publish the source to my github - I'll shoot a reply
here with that sometime in the next day or two


On Wed, Jan 3, 2018 at 8:50 AM, Alvaro Herrera 
wrote:

> Michelle Konzack wrote:
> > This is bizzar, because the URL 
> > is perfectly working for me.
>
> It fails for me exactly as Peter described.
>
> I added this entry to /etc/hosts:
>
> 54.231.120.105  pg.rsa.pub
>
> and then I could see the site.  It looks like an interesting interface.
> There are bugs related to loading pages, and the collapsing feature is a
> bit odd, but it seems promising.
>
> --
> Álvaro Herrerahttps://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
>

Re: Mailing list archiver

[Jordan Deitch]

Understood, this makes sense. Thanks for this feedback

On Wed, Jan 3, 2018 at 4:36 PM, Magnus Hagander  wrote:

>
>
> On Wed, Jan 3, 2018 at 6:53 PM, Steve Atkins  wrote:
>
>>
>> > On Jan 3, 2018, at 6:00 AM, Jordan Deitch  wrote:
>> >
>> > Thanks for the feedback! I will continue to address these issues, and I
>> intend on adding #postgresql IRC logs as well :-)
>>
>> Please don't make a public archive of #postgresql without discussion. I
>> believe the general feeling of those who use the channel is that a public
>> archive of it is not wanted.
>>
>
> Yeah, this has been discussed repeatedly in the past and the conclusion
> has always been to not do that. There are a number of people who
> specifically use the IRC channel to avoid posting to a public list, and
> they should be allowed to do so without a public archive.
>
>
> --
>  Magnus Hagander
>  Me: https://www.hagander.net/ <http://www.hagander.net/>
>  Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
>

Re: Bulk Insert/Update Scenario

[Jordan Deitch]

Hi Mana,

A starting point would be reading about the batch upsert functionality:
https://www.postgresql.org/docs/current/static/sql-insert.html

You would do something like:
INSERT INTO table ON CONFLICT update...

This operation would be atomic. You can also look into deferrable
constraints such that you would perform all your insert / update operations
in a transaction block and accommodate for the constraints.

I hope this helps to get you on the right track!

Thanks,
Jordan Deitch
http://id.rsa.pub

Re: Bulk Insert/Update Scenario

[Jordan Deitch]

INSERT .. ON CONFLICT can be ran as a bulk operation:

create table test(id int);
insert into test(id) values (1), (2), (3), (4);

Unless you mean you don't want to run this for every table?


Thanks,
Jordan Deitch
http://id.rsa.pub