by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 09 2019 17:23
    pushed to ged/ruby-pg
    21 commits
  • Oct 09 2019 17:23
    pushed to ged/ruby-pg
    0 commits
  • Oct 04 2019 04:59
    pushed to ged/ruby-pg
    8 commits
  • Oct 03 2019 20:05
    pushed to ged/ruby-pg
    2 commits
  • Oct 03 2019 20:05
    pushed to ged/ruby-pg
    0 commits
  • Oct 03 2019 18:50
    pushed to ged/ruby-pg
    Take the memory into account, that is allocated on ruby side The memory size reported to the GC and to ObjectSpace.memsize_of was only about libpq's storeage, but didn't include ruby side. (compare)
  • Oct 03 2019 18:50
    pushed to ged/ruby-pg
    0 commits
  • Oct 03 2019 11:25
    pushed to ged/ruby-pg
    Release field names to GC when clearing a PG::Result Before this field names were bound to the result until the result could be GC'ed, even after calling PG::Result#clear . (compare)
  • Oct 03 2019 11:25
    pushed to ged/ruby-pg
    0 commits
  • Sep 29 2019 18:23
    pushed to ged/ruby-pg
    Fix wrong function signature Raised as a warning in ruby-2.7. (compare)
  • Sep 29 2019 18:23
    pushed to ged/ruby-pg
    0 commits
  • Sep 29 2019 15:51
    pushed to ged/ruby-pg
    21 commits
  • Sep 29 2019 15:51
    pushed to ged/ruby-pg
    0 commits
  • Apr 02 2019 20:51
    pushed to ged/ruby-pg
    10 commits
  • Apr 02 2019 20:50
    pushed to ged/ruby-pg
    0 commits
  • Jan 09 2019 18:46
    ged pushed to ged/ruby-pg
    0 commits
  • Dec 28 2018 13:49
    larskanis pushed to ged/ruby-pg
    Describe that all rows are stored in a PG::Result Fixes #289 (compare)
  • Dec 28 2018 13:49
    larskanis pushed to ged/ruby-pg
    0 commits
  • Dec 27 2018 17:29
    larskanis pushed to ged/ruby-pg
    0 commits
  • Dec 27 2018 13:59
    larskanis pushed to ged/ruby-pg
    12 commits
Samuel Williams
@ioquatix
Of course, sometimes this behaviour is not desired, but in the end, it means there is only one place to configure the connection limit - inside the postgres server.
As it's just an experiment, that's the direction I took, but of course if you have lots of things accessing the database, you might want to limit the number of concurrent connections.
I wrote a summary blog post of a tech talk I did locally: https://www.codeotaku.com/journal/2018-03/asynchronous-ruby/index
on my homelab server which has 64G of memory and a decent amount of IO, we could sustain around 4000 requests per second
each request being 100ms
Samuel Williams
@ioquatix
I've been exploring making a simpler API for async, and I got something like this
include Async::Methods

async def count_chickens(area_name)
    10.times do |i|
        sleep rand

        puts "Found a chicken in #{area_name}!"
    end
end

async def count_all_chickens
    go {count_chickens("garden")}
    go {count_chickens("roof")}
    go {count_chickens("tree")}
end

count_all_chickens
Samuel Williams
@ioquatix
Actually, I've flagged the go method, it's superfluous
Mark Nyon
@trystant
Hi, I've got an RDS postgres instance that I want to connect to a Heroku app. I'm using Fixie Socks to provide a SOCKS5 server and now I'm looking for a way to integrate that server with pg. If there's documentation I can peruse, I'd be glad to do so. Any other feedback's also welcome. Thanks in advance
Mark Nyon
@trystant
Pinging @ged
Rubinder Singh
@rubindersingh
Hi @ged , could you please create new release as I want to use those advanced cidr, inet, typecasting methods that have been added recently
Lars Kanis
@larskanis
I uploaded a pre-release version.
Would love to get some feedback about the pre-release.
andrea_denisse.go
@da-edra
Hello, I'm having a problem with pg gem in a Rails project.

If I try to create a project with:
rails new spina_example --database=postgresql
Then cd to spina_example
And then bin/rails db:create

I get this error:
https://gist.github.com/da-edra/0b68baf9d3dfdc53c4050fa5a5b4a2ee

I've Googled the error already with no luck from the Stack Overflow and other websites solutions.
andrea_denisse.go
@da-edra
What could be the cause of this problem and how can I solve it?
I'm using Arch Linux with Ruby 2.5.0 and Rails 5.2
pg 1.0.0
Lars Kanis
@larskanis
@da-edra
You
Lars Kanis
@larskanis
need to set the host in your database.yml file. Look for postgresql.conf in /etc. It should specify the Unix domain socket to be used. Alternatively you can use a TCP connection by host: localhost .
andrea_denisse.go
@da-edra
I made a sudo find / postgresql.conf with no results.
I'm still having this problem and I don't know what could be causing it.
Lars Kanis
@larskanis
@da-edra The command should be sudo find /etc -name postgresql.conf. You might try to find some Arch Linux specific instructions. Does psql work?
Wouter Schoofs
@WouterSchoofs
Hi everybody. I have a malloc_error_break in our API developed in Ruby On Rails
Ricardo Quintana
@rqc
Hi everyone, I am becoming the owner of a rails project built with pg as a dependency. I am trying to build it in my MacOS environment and I am hitting the No pg_config... error during bundle install. I read the guidelines for solving the issue, but I am curious on why do I need to install Postgres to be able to build this gem. This could be a problem when I try to build a docker image of this rails app without Postgress installed in the same image (think microservices). Any thoughts on how I could circumvent this? Thanks!
Ricardo Quintana
@rqc
@ged let me know if you have any insight on this matter.
Yosi Attias
@yosiat
Hi,
I am seeing lots of crashes on many computers in our office
https://bitbucket.org/ged/ruby-pg/issues/291/crash
Alexander Momchilov
@amomchilov
Anyone online?
Benoit Daloze
@eregon
Hello, what CI does the pg gem use? I'd like to add TruffleRuby in pg's CI to ensure newer versions still work on TruffleRuby.
Oh, I didn't see ged/ruby-pg@be01a14 :)
It seems there is only 1 failure: https://travis-ci.org/ged/ruby-pg/jobs/595579253
Benoit Daloze
@eregon
We should try to remove it from allow_failures and just skip the not-yet-working specs, otherwise it's too easy to break and nobody will notice it
Lars Kanis
@larskanis
Hi Benoit,
Benoit Daloze
@eregon
@larskanis Hi!
Lars Kanis
@larskanis
My intension was to add TruffleRuby tentatively and when it runs
So far it looks very promising. I'm really impressed by your and your team's work!
Lars Kanis
@larskanis
I only hesitate due to the LLVM issues printed to the console like here: https://travis-ci.org/ged/ruby-pg/jobs/595579253#L781
The one failing test you mentioned is timing dependent and probably no reason to worry. I'll fix the test.
Benoit Daloze
@eregon
-Wundef warnings are fine, it's an extra warning we enable that MRI doesn't, probably we should only use it internally, not when installing gems
../../../../ext/pg_connection.c:2666:47: warning: comparison between pointer and
      integer ('int' and 'VALUE' (aka 'void *'))
        if(rb_respond_to(stream,rb_intern("fileno")) == Qfalse)
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^  ~~~~~~
is indeed not ideal, rb_respond_to returns int and so it should be == 0 to avoid the warning. Behavior-wise it should still work though because Qfalse == (int)0
and that's the only 2 kinds of warnings in that log
Lars Kanis
@larskanis
I fixed this Qfalse warning in commit ged/ruby-pg@3f1cdd7
What are the LLVM optimizer errors about? Is it something to worry? https://travis-ci.org/ged/ruby-pg/jobs/595579253#L781
Benoit Daloze
@eregon
That's a compilation failure inside TruffleRuby/Sulong. It does not affect behavior, so from pg's side I would say nothing to be done and not worrying, it's a bug on TruffleRuby/Sulong's side.
Lars Kanis
@larskanis
Alright, thanks!
Resti̸̮̇̄͐̐̇̀̒́̓̀̔̂̕͠ng Glit̸̠̠̹̯͕̐̿̊̈ch Face̶̞̐̾̓
@Dr_Berky_twitter

Hey, getting this error
'An error occurred while installing pg (1.2.2), and Bundler cannot continue.
Make sure that gem install pg -v '1.2.2' --source 'https://rubygems.org/' succeeds before bundling.'

Sanity check. the pg gem up and running right now?

Gem::Ext::BuildError: ERROR: Failed to build gem native extension.