Re: Call for Papers - PGConf.ASIA 2018
On 07/29/2018 05:59 PM, Tatsuo Ishii wrote: Hi PostgreSQL lovers, The call for papers for PGConf.ASIA 2018 will be closed on 31st July, 2018 (Japan time), that is 15:00 31st July 2018 UTC. I am looking forward to receiving your great proposals and seeing you in Akihabara (yes, like last year, the conference venue is in the "Electric City" Akihabara). -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp Hi, PGconf.ASIA 2018 will be held on December 10 to 12 in Tokyo and we are now accepting proposals for talks. Join us and other users and developers from around the world at the home of the oldest and largest user group; Japan! (See http://www.pgconf.asia/EN/2017/program/ for last year's conference program). - About the conference: Location: Akihabara convention hall (Tokyo) http://www.akibahall.jp/data/outline_eng.html Targeted number of attendees: 700 in total http://www.pgconf.asia/EN/2018/ - About the call for papers: - To submit a paper, please include the following details and send to: pgconf-asia-2018-submission(at)pgconf(dot)asia Title Abstract Description Language spoken during the talk: Japanese or English Language of the talk material: Japanese and/or English - Submission deadline is midnight, 31st July, 2018 (Japan time). - Submissions should be sent in English, Japanese, or both. Japanese-only submissions will be translated into English for discussion within the program committee. - Presentation materials will be released the day after the conference and will be made available to the public. The copyright of the material will be retained by the author. We ask that you share your materials under a Creative Commons license: https://creativecommons.org/licenses/by-nc-nd/4.0/ If your presentation material cannot be shared, please let us know. - Talks may be recorded or photographed. In both cases, the content may be made public under a Creative Commons license: https://creativecommons.org/licenses/by-nc-nd/4.0/. The copyright of the material is retained by the speaker. - Speakers will be informed of the result of the selection by the end of August. Speakers will be requested to submit brief biographies and photos to be published in the conference program. - The exact length of each session is not decided yet (Last year it was 40 minutes and we expect no big change for this year). +1 JD -- Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc *** A fault and talent of mine is to tell it exactly how it is. *** PostgreSQL centered full stack support, consulting and development. Advocate: @amplifypostgres || Learn: https://postgresconf.org * Unless otherwise stated, opinions are my own. *
Re: Call for Papers - PGConf.ASIA 2018
Hi PostgreSQL lovers, The call for papers for PGConf.ASIA 2018 will be closed on 31st July, 2018 (Japan time), that is 15:00 31st July 2018 UTC. I am looking forward to receiving your great proposals and seeing you in Akihabara (yes, like last year, the conference venue is in the "Electric City" Akihabara). -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp >> Hi, >> >> PGconf.ASIA 2018 will be held on December 10 to 12 in Tokyo and we are >> now accepting proposals for talks. >> >> Join us and other users and developers from around the world at the >> home of the oldest and largest user group; Japan! >> >> (See http://www.pgconf.asia/EN/2017/program/ for last year's >> conference program). >> >> - About the conference: >> Location: Akihabara convention hall (Tokyo) >> http://www.akibahall.jp/data/outline_eng.html >> Targeted number of attendees: 700 in total >> http://www.pgconf.asia/EN/2018/ >> >> - About the call for papers: >> >> - To submit a paper, please include the following details and send to: >> pgconf-asia-2018-submission(at)pgconf(dot)asia >> >> Title >> Abstract >> Description >> Language spoken during the talk: Japanese or English >> Language of the talk material: Japanese and/or English >> >> - Submission deadline is midnight, 31st July, 2018 (Japan time). >> >> - Submissions should be sent in English, Japanese, or both. >> Japanese-only submissions will be translated into English for >> discussion within the program committee. >> >> - Presentation materials will be released the day after the conference >> and will be made available to the public. The copyright of the >> material will be retained by the author. >> >> We ask that you share your materials under a Creative Commons >> license: https://creativecommons.org/licenses/by-nc-nd/4.0/ >> >> If your presentation material cannot be shared, please let us know. >> >> - Talks may be recorded or photographed. In both cases, the content >> may be made public under a Creative Commons license: >> https://creativecommons.org/licenses/by-nc-nd/4.0/. The copyright >> of the material is retained by the speaker. >> >> - Speakers will be informed of the result of the selection by the end >> of August. Speakers will be requested to submit brief biographies and >> photos to be published in the conference program. >> >> - The exact length of each session is not decided yet (Last year it >> was 40 minutes and we expect no big change for this year). >> >> Suggested topic areas include but not limited to: >> >> - Large-scale PostgreSQL deployments. >> - Migrations from other databases to PostgreSQL >> - Operations and administration >> - Performance and feature implementation >> - Replication, clustering, HA, sharding. >> - Tools and utilities for PostgreSQL >> - Benchmarking and hardware, tuning. >> - PostgreSQL community and hacking. >> - Studies, surveys on PostgreSQL ecosystem >> - Asian PostgreSQL community & user groups >> - Data warehousing >> - Location-aware and mapping software with PostGIS >> - Research and teaching with PostgreSQL >> - Case studies, including but not limited to: IoT/Cloud, Healthcare, >> Education and Academy >> >> - If you have any questions regarding the event, feel free to contact >> the organization committee at >> pgconf-asia-2018-submission(at)pgconf(dot)asia(dot) >> >> See you in Tokyo :) >> >> PGConf.ASIA 2018 Steering Committee >> http://www.pgconf.asia/EN/2018/ >> [Please feel free to redistribute this CFP] >> >
Re: postgres with xcode
Well in that case, do you have something in mind. Perhaps a prototype which has a some research component which can teach us something interesting. In the course we are divided into teams of 4 and we are going to work on the project for 2-3 months. I know such I'm asking for too much but just giving it a shot really. :) On Sun, Jul 29, 2018 at 9:26 PM Tom Lane wrote: > Sumit Chaturvedi writes: > > So I wanted to play around with Postgresql itself. I have looked at the > > TODO list and it has given me a lot of ideas. If anyone has any > > thoughts/ideas which they didn't have time to pursue but are interesting, > > please let me know? > > Cool, but be warned that most of the stuff on the TODO list is either > obsolete or hard (sometimes more hard-to-get-consensus-for than hard- > to-do-technically). We don't maintain that list very well :-( > > regards, tom lane > -- Sumit Chaturvedi
Re: postgres with xcode
Sumit Chaturvedi writes: > So I wanted to play around with Postgresql itself. I have looked at the > TODO list and it has given me a lot of ideas. If anyone has any > thoughts/ideas which they didn't have time to pursue but are interesting, > please let me know? Cool, but be warned that most of the stuff on the TODO list is either obsolete or hard (sometimes more hard-to-get-consensus-for than hard- to-do-technically). We don't maintain that list very well :-( regards, tom lane
Re: postgres with xcode
Thanks a lot for spending time to write all these elaborate answers. They were all really helpful. Finally I gave up on xcode and switched to eclipse. Probably for the best. I was attempting to do all this in the first place because in our course in college, we have to do a project. Almost all people make a web/mobile app which simply uses a database. I felt that this wasn't a right project to do if one really wanted to learn about databases. So I wanted to play around with Postgresql itself. I have looked at the TODO list and it has given me a lot of ideas. If anyone has any thoughts/ideas which they didn't have time to pursue but are interesting, please let me know? With warm regards On Sun, Jul 29, 2018 at 8:06 PM, Tom Lane wrote: > Sumit Chaturvedi writes: > > So although the problem is with xcode. I have a feeling that it is not > > because of LC_ALL. > > So my point is that maybe the hint is not entirely correct.. > > At the time that HINT was written, the only reason we knew of for a > production postmaster to become multithreaded under macOS was for libintl > to start an extra thread while trying to find out the default locale. > That could be prevented by setting LC_ALL, hence the hint. > > I wonder whether starting the postmaster under xcode inherently > causes extra threads to be present (for debugging?). There are > quite a number of PG developers who use Macs, including me, but > I don't use xcode for PG and I think others don't either. > > In any case, I concur with the upthread advice not to take out > the anti-multithreading check. The postmaster will not work > reliably if there are extra threads in it, so you'd just be > dooming yourself to crashes and frustration. > > Usually the thing you want to trace is not the postmaster anyway, > but some session backend. The best bet is to start the postmaster > normally, start psql or your other client of choice, then identify > which backend process is connected to that client and attach to it > with gdb/lldb. Perhaps xcode can do an "attach to running process", > though at this point I'm wondering if it starts extra threads when > it does so. > > regards, tom lane > -- Sumit Chaturvedi
Re: postgres with xcode
Sumit Chaturvedi writes: > So although the problem is with xcode. I have a feeling that it is not > because of LC_ALL. > So my point is that maybe the hint is not entirely correct.. At the time that HINT was written, the only reason we knew of for a production postmaster to become multithreaded under macOS was for libintl to start an extra thread while trying to find out the default locale. That could be prevented by setting LC_ALL, hence the hint. I wonder whether starting the postmaster under xcode inherently causes extra threads to be present (for debugging?). There are quite a number of PG developers who use Macs, including me, but I don't use xcode for PG and I think others don't either. In any case, I concur with the upthread advice not to take out the anti-multithreading check. The postmaster will not work reliably if there are extra threads in it, so you'd just be dooming yourself to crashes and frustration. Usually the thing you want to trace is not the postmaster anyway, but some session backend. The best bet is to start the postmaster normally, start psql or your other client of choice, then identify which backend process is connected to that client and attach to it with gdb/lldb. Perhaps xcode can do an "attach to running process", though at this point I'm wondering if it starts extra threads when it does so. regards, tom lane
Re: postgres with xcode
On 07/29/2018 02:03 AM, Sumit Chaturvedi wrote: Hello, Does the following seem unusual? amaltaas:backend amaltaas$ locale LANG="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_CTYPE="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_ALL= After this I ran postgres from terminal like the following and it works: amaltaas:backend amaltaas$ ./postgres -D ~/Desktop/dn 2018-07-29 14:27:04.544 IST [68250] LOG:listening on IPv6 address "::1", port 5432 2018-07-29 14:27:04.545 IST [68250] LOG:listening on IPv6 address "fe80::1%lo0", port 5432 2018-07-29 14:27:04.545 IST [68250] LOG:listening on IPv4 address "127.0.0.1", port 5432 2018-07-29 14:27:04.546 IST [68250] LOG:listening on Unix socket "/tmp/.s.PGSQL.5432" 2018-07-29 14:27:04.567 IST [68251] LOG:database system was shut down at 2018-07-29 14:23:35 IST 2018-07-29 14:27:04.574 IST [68250] LOG:database system is ready to accept connections So although the problem is with xcode. I have a feeling that it is not because of LC_ALL. So my point is that maybe the hint is not entirely correct.. Could be, it is a hint not a requirement. Have you tried unsetting the LC_ALL variable in xcode? -- Adrian Klaver adrian.kla...@aklaver.com
