Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / brianc/node-pg-pool issues and pull requests

#140 - Ambiguous connection timeout parameter

Issue - State: closed - Opened by vitaly-t over 4 years ago

#139 - Cloud Functions: Query timeout with max = 1

Issue - State: closed - Opened by seriousManual over 4 years ago - 5 comments

#138 - pool.on('error') Documentation Inaccurate

Issue - State: open - Opened by jerroydmoore over 4 years ago

#137 - Bump js-yaml from 3.12.0 to 3.13.1

Pull Request - State: closed - Opened by dependabot[bot] over 4 years ago
Labels: dependencies

#136 - Bump lodash from 4.17.11 to 4.17.13

Pull Request - State: closed - Opened by dependabot[bot] over 4 years ago
Labels: dependencies

#135 - min connections support

Issue - State: closed - Opened by djcuvcuv over 4 years ago - 5 comments

#134 - pool.end() resolves before the last pool.query()

Issue - State: open - Opened by ghost almost 5 years ago
Labels: bug

#132 - pool.end() needs to process pending queries

Issue - State: open - Opened by ghost almost 5 years ago - 1 comment

#131 - Handle client errors in pool.query

Pull Request - State: closed - Opened by johanneswuerbach almost 5 years ago - 5 comments

#130 - 字段类型int8

Issue - State: open - Opened by JamesRen88 almost 5 years ago - 1 comment

#129 - Minor cleanup - inline throwOnRelease()

Pull Request - State: closed - Opened by nyurik almost 5 years ago - 1 comment

#128 - Update standard package to latest (14.1.0)

Pull Request - State: open - Opened by fanatid almost 5 years ago

#127 - Exception thrown in _remove

Issue - State: open - Opened by EricRMeyer about 5 years ago

#126 - Remove reference to "min" config option

Pull Request - State: closed - Opened by jbaudanza about 5 years ago - 1 comment

#125 - Implement 'release' event and 'activeCount' property.

Pull Request - State: open - Opened by PrimeJunta about 5 years ago - 4 comments

#124 - Emit 'release' event and add 'activeCount' gettable property to pool

Issue - State: open - Opened by PrimeJunta about 5 years ago - 1 comment

#123 - Remove idleListener when client is in-use

Pull Request - State: closed - Opened by johanneswuerbach about 5 years ago - 8 comments

#122 - release should reset state of connection

Issue - State: open - Opened by daurnimator over 5 years ago - 1 comment

#121 - node-postgres already has connection pooling built in...

Issue - State: closed - Opened by johncmunson over 5 years ago - 1 comment

#120 - Is there a difference between pool.query() VS connect(), query(), release()

Issue - State: closed - Opened by gajus over 5 years ago - 2 comments

#119 - Prevent requeuing a broken client

Pull Request - State: open - Opened by johanneswuerbach over 5 years ago

#118 - fix for cases where connection is broken and release() is called, avo…

Pull Request - State: open - Opened by olgkpln over 5 years ago - 4 comments

#116 - Connection terminated due to connection timeout / Connection terminated

Issue - State: open - Opened by dustin-H over 5 years ago - 16 comments

#115 - Prevent double release with callback

Pull Request - State: closed - Opened by johanneswuerbach over 5 years ago - 8 comments

#114 - Upgrade to test on node 10

Pull Request - State: closed - Opened by brianc over 5 years ago - 3 comments

#112 - Use double-ended queue to improve performance

Pull Request - State: closed - Opened by Chocobozzz over 5 years ago - 4 comments

#111 - Fix queued checkout after a connection failure

Pull Request - State: closed - Opened by charmander over 5 years ago - 3 comments
Labels: bug

#110 - Max checkout timeout event

Pull Request - State: open - Opened by johanneswuerbach over 5 years ago - 5 comments

#109 - Fix two races

Pull Request - State: closed - Opened by johanneswuerbach over 5 years ago - 16 comments

#108 - Support async_hooks

Issue - State: open - Opened by chrisdickinson over 5 years ago - 1 comment

#106 - Fix _endCallback

Pull Request - State: open - Opened by fanatid over 5 years ago - 4 comments

#105 - High latency after 10 queries

Issue - State: closed - Opened by michaelgrn almost 6 years ago - 4 comments

#104 - Problems with config.min

Issue - State: closed - Opened by thosaa almost 6 years ago - 2 comments

#103 - Is there an event triggered when the pool is being drained?

Issue - State: open - Opened by kilianc almost 6 years ago - 1 comment

#102 - Is a pool gracefully closing db connections when node.js exits?

Issue - State: closed - Opened by rmoestl about 6 years ago - 2 comments
Labels: question

#101 - Notify/Listen, Keep connection for ever

Issue - State: open - Opened by vaggeliskls about 6 years ago

#100 - Changing connection string in Pool's life cycle

Issue - State: open - Opened by tihomirmagdic about 6 years ago - 3 comments

#99 - pool not timing out/idling

Issue - State: open - Opened by InsidiousForce about 6 years ago - 1 comment

#98 - Only count processes that are connected to a database

Pull Request - State: closed - Opened by tomhughes over 6 years ago - 3 comments

#97 - Race condition in pool.on('connect',...) ?

Issue - State: open - Opened by claytongulick over 6 years ago - 8 comments

#96 - pool.end() does not return a proper promise

Issue - State: open - Opened by riimeik over 6 years ago

#95 - can only pool max size errors be caught?

Issue - State: open - Opened by ouyangxuanyun over 6 years ago - 1 comment

#94 - Typo in "Connection terminated" error message

Pull Request - State: closed - Opened by bigman73 over 6 years ago - 2 comments

#93 - this.log is not a function

Issue - State: open - Opened by mike-aungsan over 6 years ago - 1 comment

#92 - Testing with fakeTimers and pg-pool results in "Connection terminated by user"

Issue - State: closed - Opened by TheFive over 6 years ago - 1 comment

#91 - Getting stuck

Issue - State: closed - Opened by pencilcheck over 6 years ago - 6 comments

#90 - How to specify the ssl certificate for connection

Issue - State: closed - Opened by samehsharaf over 6 years ago - 1 comment

#89 - Bad spelling in error message =) sorry... i couln't resist

Issue - State: closed - Opened by mzalazar over 6 years ago - 1 comment

#88 - Update CI versions

Pull Request - State: closed - Opened by charmander over 6 years ago - 3 comments

#87 - Count only test query itself

Pull Request - State: closed - Opened by charmander over 6 years ago

#86 - Remove timed-out checkouts from queue correctly

Pull Request - State: closed - Opened by charmander over 6 years ago - 3 comments

#85 - Connection timeout with full connection pool overwrites callback queue

Issue - State: closed - Opened by freitagbr over 6 years ago - 13 comments

#84 - Properly handling transactions with pg-pool

Issue - State: closed - Opened by officer-rosmarino over 6 years ago

#83 - idleListener no longer grabs references to things it doesn't need

Pull Request - State: closed - Opened by lykkin over 6 years ago - 36 comments

#82 - Do not return broken connections to the idle pool

Pull Request - State: open - Opened by boromisp over 6 years ago

#81 - Release called on client which has already been released to the pool

Issue - State: closed - Opened by SunYuanOnly over 6 years ago - 1 comment

#80 - Using quotes in query ignores parameters inside the quotes

Issue - State: closed - Opened by modulitos over 6 years ago - 3 comments

#79 - Promise pg pool connect (v1.8.0)

Pull Request - State: closed - Opened by hadasiii almost 7 years ago

#78 - terminiated -> terminated

Pull Request - State: closed - Opened by ubershmekel almost 7 years ago

#77 - How to specify an optimal number for the max size of Pool

Issue - State: open - Opened by phongyu almost 7 years ago - 1 comment
Labels: question

#76 - Unhandled promise rejection

Issue - State: closed - Opened by phongyu almost 7 years ago - 3 comments

#75 - Docs : document option log

Issue - State: open - Opened by abenhamdine almost 7 years ago

#74 - Dropping generic-pool's FIFO option is a regression

Issue - State: closed - Opened by jgwmaxwell almost 7 years ago - 2 comments

#73 - Clarifying pool connect logging

Pull Request - State: closed - Opened by ubershmekel almost 7 years ago - 1 comment

#72 - docs: document the remove event

Pull Request - State: closed - Opened by gajus almost 7 years ago - 5 comments

#71 - Fix client remove clearing unrelated idle timers

Pull Request - State: closed - Opened by charmander almost 7 years ago - 2 comments

#70 - Add connection & query timeout if all clients are checked out

Pull Request - State: closed - Opened by brianc almost 7 years ago - 1 comment

#69 - Get number of active clients

Issue - State: closed - Opened by chiluap almost 7 years ago - 3 comments

#68 - Fix idle client teardown on error

Pull Request - State: closed - Opened by brianc almost 7 years ago - 1 comment

#67 - 2.0

Pull Request - State: closed - Opened by brianc almost 7 years ago - 6 comments

#66 - How to access clients from exported pool for release and then pool.end?

Issue - State: closed - Opened by dman777 almost 7 years ago - 4 comments

#64 - Does idleTimeoutMillis = -1 keep connections open indefinently

Issue - State: closed - Opened by joekiller about 7 years ago - 2 comments

#61 - Add interface to generic-pool getters

Pull Request - State: closed - Opened by lenemson about 7 years ago - 2 comments

#60 - Performance/structure of app

Issue - State: closed - Opened by brandonros about 7 years ago - 8 comments

#59 - Adding support for `isDestroyed` function

Pull Request - State: closed - Opened by vitaly-t about 7 years ago - 4 comments

#58 - Fails to reconnect after invoking end()

Issue - State: closed - Opened by vitaly-t about 7 years ago - 12 comments

#57 - Client is missing in error handling

Issue - State: closed - Opened by vitaly-t about 7 years ago - 6 comments

#56 - drop support of node <4 ?

Issue - State: closed - Opened by abenhamdine about 7 years ago

#54 - Create LICENSE

Pull Request - State: closed - Opened by amilajack about 7 years ago - 1 comment

#53 - support sspi

Issue - State: open - Opened by amhuhn2 about 7 years ago - 1 comment
Labels: enhancement

#51 - Prevent client reuse after release

Pull Request - State: closed - Opened by kjdelisle about 7 years ago - 5 comments

#50 - Prevent reuse of released client instances

Issue - State: open - Opened by kjdelisle about 7 years ago - 10 comments

#48 - Returning client to pool after error

Issue - State: closed - Opened by maxpain over 7 years ago - 5 comments

#47 - UnhandledPromiseRejectionWarning when connection fails, .catch() not firing

Issue - State: closed - Opened by PrimeLens over 7 years ago - 22 comments

#46 - do query on new connection

Issue - State: closed - Opened by yawhide over 7 years ago - 10 comments

#45 - pg dependency

Issue - State: closed - Opened by spudly over 7 years ago - 3 comments

#43 - Add connectionSetup as configuration option to prepare a client

Pull Request - State: open - Opened by bramkoot over 7 years ago - 7 comments

#41 - connection string for pg-native

Issue - State: closed - Opened by nonword over 7 years ago - 3 comments

#40 - Notification event does not work

Issue - State: closed - Opened by Globik over 7 years ago - 4 comments

#38 - 1.6.0 broke backward compatibility by returning undefined on connect()

Issue - State: closed - Opened by diegoperini over 7 years ago - 5 comments

#37 - No error in persistent connections timeout

Issue - State: closed - Opened by chiluap over 7 years ago - 1 comment

#34 - Proper clean up?

Issue - State: closed - Opened by YourDeveloperFriend over 7 years ago - 1 comment

#33 - Pool with Promises in Lambda Propagates to Node

Issue - State: closed - Opened by mladlow over 7 years ago - 5 comments

#29 - Upgrade to generic-pool v3

Issue - State: closed - Opened by sandfox almost 8 years ago - 6 comments

#27 - What is the proper way to use transactions with async/await promises?

Issue - State: closed - Opened by rightaway almost 8 years ago - 8 comments

#24 - pg-pool swallows errors

Issue - State: closed - Opened by cressie176 almost 8 years ago - 12 comments
Labels: bug