Re: [GENERAL] Pattern Matching question - PG 9.6

2017-05-15 Thread matshyeq
^/testfile/client/[0-9]+/attachment/([0-9]{1,14}/master/$|unassigned/) Kind Regards ~Maciek On 15 May 2017 at 06:21, Patrick B wrote: > > > 2017-05-15 16:10 GMT+12:00 David G. Johnston : > >> On Sunday, May 14, 2017, Patrick B wrote: >> >>> >>> Demo: http://dbfiddle.uk/?rdbms=postgres_9.6&fiddl

Re: [GENERAL] Regex "embedded options" does only work on the whole pattern?

2016-01-05 Thread matshyeq
sdf'; my @res = $testr =~ /a(?i:sd)f/g; print @res; - asdf asDf aSDf aSdf Thank you, Kind Regards ~Maciek On 4 January 2016 at 03:58, Tom Lane wrote: > matshyeq writes: > > I can see postgresql claims to supports regular expression flags: > > Yup. > > > What I find

[GENERAL] Regex "embedded options" does only work on the whole pattern?

2016-01-03 Thread matshyeq
Hi, I can see postgresql claims to supports regular expression flags: http://www.postgresql.org/docs/current/static/functions-matching.html#POSIX-EMBEDDED-OPTIONS-TABLE which I suppose aims to be the equivalent of perl's *(?adluimsx-imsx:pattern)

Re: [GENERAL] libpq - lack of support to set the fetch size

2014-03-12 Thread matshyeq
On Wed, Mar 12, 2014 at 9:30 AM, Marko Kreen wrote: > On Tue, Mar 11, 2014 at 12:39:12PM +0000, matshyeq wrote: > > - when using PQsetSingleRowMode() function - does it give an option to > > define how many rows to cache on client's side (like JDBC setFetchSize() >

Re: [GENERAL] libpq - lack of support to set the fetch size

2014-03-12 Thread matshyeq
> > > Well, I don't know what "streamed" exactly means here. > > If server pushes sequentially all the data not asking client if ready > to > > receive then that's what the issue is about. > > This problem is handled in kernel's TCP stack - it will slow down > the connection if userspace does not

Re: [GENERAL] libpq - lack of support to set the fetch size

2014-03-11 Thread matshyeq
Marko, Tom, Adrian, Jeff, Daniel - thank you all for valuable feedback! Two general questions: - when using PQsetSingleRowMode() function - does it give an option to define how many rows to cache on client's side (like JDBC setFetchSize() does) or leaves it at pqlib's discretion? - is it/would

Re: [GENERAL] libpq - lack of support to set the fetch size

2014-03-10 Thread matshyeq
t; So probably the best is to ask Greg to speak to details if still unclear. Kind Regards, Maciek On Mon, Mar 10, 2014 at 9:42 AM, Albe Laurenz wrote: > matshyeq wrote: > > Postgresql is there for a good while perceived as one of the best (or > just simply the best!?) > > availa

Re: [GENERAL] libpq - lack of support to set the fetch size

2014-03-10 Thread matshyeq
7;m really surprised this functionality is not yet supported... On Mon, Mar 10, 2014 at 6:58 AM, Albe Laurenz wrote: > Daniel Verite wrote: > > matshyeq wrote: > > [ runs out of memory on the client because all results from a large query > are retrieved at once ] > > >>

[GENERAL] libpq - lack of support to set the fetch size

2014-03-09 Thread matshyeq
Hello, I've found an issue when tried to implement fetching rows from big table (2mln rows) in my app. Basically I don't find an elegant and easy way (other than always use cursors) to limit the number of rows returned. This causes my application to break due to the excessive memory consumption.