only dependent on input variables and are not modifying any global data.
You'll want to be careful with that. Nothing stops an immutable function
referencing a cache in a C global that it initializes one and then
treats as read only, for example.
I suspect you'll need a per-function whi
For this kind of testing I've
tended to just set conditional breakpoints in gdb, wait until they trap,
then once everything's lined up release the breakpoints in both sessions
as simultaneously as possible. Not perfect, but has tended to work.
--
Craig Ringer
t to the client like they
already are, rather than trying to stash them in server memory and
address them for returning later. Though a tuplestore could always be
used to spill to disk, I guess.
Anyway. Random idea for the day.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreS
apply. Surely this is harmless?
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
>From 2a115f7b62dbe3f98ef2c011f3283a41af86fd15 Mon Sep 17 00:00:00 2001
From: Craig Ringer
Date: Fri, 29 Aug 2014 10:00:40 +0800
Sub
ey at
input time because "EST" is always +1000 while Australia/Sydney could
also be EDT +1100 . I hate time zones. It'd probably have to expand
abbrevs to their UTC offsets at input time.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7
In the case of mean, for example, it'd just mean adding the counts and sums.
However, I'm not sure how interesting that is without the ability to
execute the subplans in parallel.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Train
master) may have many backends, each
of which may run queries in series but not in parallel. Any given
process may only run one query at once.
> but it
> seems like if I am using SPI I could only run one query at a time - it's
> not an asynchronous API.
Correct.
> Any h
t
something we allow in PL/PgSQL, though; from the outside a PL/PgSQL
function is pretty opaque to callers.
That's not to say I'm keen on a "plpgsql2" unless there's no other way;
I'd be rather happier with language version pragmas or similar. But I
don't thi
itely nicer when you just want the results in a client.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscript
t index
> 2. Aquire ACCESS EXCLUSIVE LOCK to target table( and transaction starts)
> 3. Swap old and new index
> 4. Drop old index
> 5. COMMIT
How do you handle indexes tied to constraints - PRIMARY KEY, UNIQUE, or
EXCLUSION constraint indexes?
My understanding was that this curre
in plpgsql2:
- Accept RECORD input, dynamic access to fields of records without
resorting to hstore hacks. This is certainly my #1.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing
x27;customers';
you don't want to suddenly be issuing a
DROP TABLE customers;
... which is why I suspect this might need to be not 100% backward
compatible, perhaps requiring a variable-marker prefix.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL D
FROM ?tablename
DROP TABLE ?tablename
or whatever your favourite place-holder syntax is.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To mak
hing that wasn't otherwise legal as an
identifier.
I don't love how it works now, but I don't have a better answer really.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers maili
but changing it would require making a
big mess elsewhere that's not worth doing.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chan
I FROM %I WHERE $1", col, tbl) USING val;
is not lovely. It works, but it's clumsy.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
things like this. If we
> want to, then we also want a new language.
Given how much bike shedding occurs around trivial features, can you
imagine how long that'd take?
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training &am
ing back arrays of tuples isn't very
interesting or, IMO, hugely useful for the kind of apps that want to
avoid JDBC/libpq. Especially webapps.
Close care to security and auth would also need to be taken. You don't
want to be sending a username/password with each request; you ne
rrent infrastructure? What can't
be done that should be able to be done in those languages?
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql
/en.wikipedia.org/wiki/PL/SQL) which in turn owes its heritage to
Ada and Pascal.
It serves an important role. I'm not going to pretend it's pretty, but
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
with a convincing PL/SQL compatibility layer then
it'd be worth considering adopting - when it was ready. But of course,
anyone who does the work for that is quite likely to want to sell it to
cashed-up Oracle users looking to save a few hundred grand on per-CPU
licensing.
--
Craig Ringer
On 09/01/2014 11:19 PM, Joel Jacobson wrote:
> On Mon, Sep 1, 2014 at 5:16 PM, Craig Ringer wrote:
>> On 09/01/2014 10:41 PM, Joel Jacobson wrote:
>>> This is exactly why we need a new language.
>>> All the clumsy stuff we cannot fix in plpgsql, can easily be fixed in
pl_exec.c .
Any other language that can run embedded into the PostgreSQL backend can
do the same.
PL/Python does it:
http://www.postgresql.org/docs/current/static/plpython-database.html
(though unfortunately the PL/Python interface for SQL does't follow the
Python DB-API).
PL/V8, PL/Lua, PL/Rub
Y constraint backed by a UNIQUE index.
> This patch contains some limitation.
> Also I'm thinking to implement to handle these cases.
My understanding from the prior discussion is that any satisfactory
solution to those problems would also make it possible to support
REINDEX CONCURRENTL
care to touch ... even ignoring the fact that cutting off
> EDB's air supply wouldn't be a good thing for the community to do.
Yep. Especially as PL/SQL is not a lovely language to work with anyway;
if the goal was "a better built-in PL" then PL/SQL wouldn't be
rtitioning key.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
s week]
could benefit from it, but they also need things like online
repartitioning, updates to move tuples across partitions, etc.
So it's all in the "let's not lock it out for the future, but lets not
tackle it now either" box.
--
Craig Ringer http:
ng with using format() for dynamic queries and why is the
> approach not more prominent or recommended?
Historical, really.
> And the format function option is not even listed in the section on quoting
> (40.11.1. Handling of Quotation Marks)
That's a real oversight that ne
be told by the
server "Please upgrade to transport level security before proceeding".
I like how IMAP does it, where the server announces its capabilities.
Reasonable to aim for in a protocol v4?
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development
this solves.
I know why the changes in 8.3 were made, and they're clearly beneficial
overall, but we need to start putting some more implicit casts from text
to text-like types in, especially where there's no SQL-standard type
that users of JDBC etc can easily use in mappings.
--
Craig Ringe
an, and the sheer scope of the
endeavour.
It's not going from 50% compatible to 80% compatible, it's going from 5%
compatible to 7% compatible. The most used 5% maybe, but still...
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
om/q/14884955/398670
http://stackoverflow.com/q/10898369/398670
... and that's just what I can find in a few minutes' searching on one site.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
tion, and it's wrong most of the time when the parameter really is
just text.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chang
urrently sends 'varchar' for string types, and the
user has a 'varchar' and 'text' overload of the same function defined,
it'd change the overload selected. That's a (tiny) BC break.
Perhaps the solution here is just to make 'unknown' the default
round `raise` in PL/PgSQL for use in `CASE` statements etc.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
ht
his area.
Well, you have Petr's for RAISE EXCEPTION ... WHEN, and I'd also like
that or RAISE ASSERT ... WHEN.
Much (much) saner than the other proposals on this thread IMO.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Train
; containing the current Aussie zone abbreviations, so as to provide
> an easy way to maintain backwards compatibility at need (you'd select
> that as your timezone_abbreviations GUC setting).
>
> Anyone from down under care to remark about the actual usage of old
> and new abbreviation
ould be unable to run the Pg release or
take a massive performance hit, but that doesn't appear to be the case here.
So I'm all for taking advantage of the hardware support.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training &am
yte might be
worthwhile at the same time. It seems likely that there'll be more room
for improvement in jsonb, possibly even down to using different formats
for different data.
Is it worth paying a byte per value to save on possible upgrade pain?
--
Craig Ringer http://w
block is much
easier, and the idea just rings wrong to me.
I agree with Pavel that the natural way to parameterise DO blocks, down
the track, will be to allow them to get (and set?) SQL-typed session
variables. Of course, we'd need to support them first ;-)
--
Craig Ringer
poster to some resources and more
appropriate mailing lists.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
.com/q/25876287/398670 to -hackers.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ng support
for older platforms I suggest that we start with just switching over to
GetSystemTimeAsFileTime, which has been supported since Windows 2000.
Then more precise time capture can be added in a later patch.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Develop
On 09/17/2014 11:19 PM, Andrew Dunstan wrote:
>
> On 09/17/2014 08:27 AM, Craig Ringer wrote:
>> Hi all
>> On Windows 2012 and Windows 8 I'd like to use the new
>> GetSystemTimePreciseAsFileTime call instead. As this requires some extra
>> hoop-jumping to sa
as
Win2k it's not going to worry anybody.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://
no way of knowing it isn't in the current
client_encoding, and no way of telling what encoding it is anyway.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list
ut the idea that minor release, supposedly safe updates
> think they can whack this around without breaking applications really
> kind of blows my mind.
If confirmed, it certainly requires some ... firm ... bug reports.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreS
tore already knows to tell you to use psql if it sees an SQL file
as input. Having something similar for pg_dump would be really useful.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers
"git am --3way" helps a lot, but only if the
patch is created with "git format-patch".
Perhaps it's time to look at whether git can do more to help us with the
testing and review process.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Developme
in
getting involved in developing extensions or feature work?
See:
http://www.postgresql.org/developer/
If that's *not* what you're trying to do, then perhaps you want the
tutorial, main documentation, and pgsql-general mailing list?
--
Craig Ringer http://www
at least twice already that this kind of solution is bad,
> I don't know of any change that would invalidate the reasons for
> deciding that way so I don't see why they would suddenly become
> acceptable...
All good points. I was wrong to suggest just going for TEMPORARY
FU
erflow post is
http://stackoverflow.com/q/26005359/398670 .
where I answered in some detail.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.or
scope.
>
> I'll take a look at doing this in the next couple days, and see
> whether doing it that way is as easy as it seems on the face of it.
Oracle's TABLE variables in PL/SQL are quite similar; it might be worth
observing how they work for comparison.
--
Craig Ringer
than a giant squashed patch as an attachment.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.post
n top
of master).
I got in the habit while working on RLS, to keep me sane with that
patchset, and find it works well for me.
However, everyone has a different work style. Colour me happy if it's in
git at all.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL
happy to help with documenting it.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
stackoverflow.com/q/237327/398670
Useful article:
http://michaeljswart.com/2011/09/mythbusting-concurrent-updateinsert-solutions/
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (
On 09/29/2014 12:03 PM, Peter Geoghegan wrote:
> On Sun, Sep 28, 2014 at 8:53 PM, Craig Ringer wrote:
>> there's an alarming lack of concern for concurrency, just a couple of
>> links to :
>>
>> http://www.mssqltips.com/sqlservertip/3074/use-caution-with-sql-ser
mary mail? Something else?
We have https://wiki.postgresql.org/wiki/SQL_MERGE but it's outdated,
pretty sparse, and not really about the current work.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgs
n (this is not true of Oracle's READ COMMITTED, for example).
That's useful to know, and certainly worth covering in the isolation
portion of the docs.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgs
kinds of statement with subtly
different syntax differentiating them.
Upsert is full of confusing and subtle behaviour. Any implementation
needs to focus on making it easy to get right, and I don't think having
something where small syntax variations can cause you to silently trip
out of the conc
ems to be specified as more of an OLAP / ETL operation than an
OLTP one, and I think we should probably respect that - and the way
other RDBMSes have already implemented it.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Service
n of a prepared statement against a list of
params, then a single Sync at the end.
> Can someone please let me know what the recommended/best practice here
> would be?
You might want to check out what PgJDBC does; it's fairly sane in this area.
--
Craig Ringer http:
lovely.
I would like to be able to specify a top-level option at Bind/Execute
time that asks the server to send binary for built-in types only, or for
a list of oids that we register ourselves as understanding binary for at
a session level. That would require a protocol change, though.
It mi
eful
library of perf-based diagnostics and tracing tools for PostgreSQL.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
;s really the same as the upsert case. I guess I also
just don't really understand the utility of insert ... on conflict
ignore for GiST exclusion constraints.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
S
esql.org/wiki/UPSERT#Adopting_an_existing_non-standard_syntax
which I'd appreciate it if you could fill out based on your existing
research and notes. I don't think it makes sense for me to write those
when you've already done the required study/note taking and just need to
transfer
eas
about the feasibility of adding such support.
I didn't have much luck searching for discussion on the matter.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsq
d on perceived merit and on how effectively you explain the utility
of the changes you want to make.
Some companies find it easier to work via partners experienced with the
development model; again, you can find candidates at
http://www.postgresql.org/support/professional_support/ .
--
Craig Ringe
nly to have it
rejected, or to find that you've fixed a problem that really stemmed
from a misunderstanding of how something works.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing
yping alone...
I think we just need to add support for client-side parameter binding of
literals with a client-side flag, or by detecting statement type. So
users still get to use bind parameters, but PgJDBC deals with the details.
--
Craig Ringer http://www.2ndQuadrant.com/
ks captured - what tool?
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 10/10/2014 04:16 AM, MauMau wrote:
> From: "Craig Ringer"
>> It'd be interesting and useful to run this test on a debug build of
>> PostgreSQL, i.e. one compiled against the debug version of the C library
>> and with full debuginfo not just minimal .pdb.
>
On 09/17/2014 08:27 PM, Craig Ringer wrote:
> Hi all
>
> Attached is a patch to switch 9.5 over to using the
> GetSystemTimeAsFileTime call instead of separate GetSystemTime and
> SystemTimeToFileTime calls.
Following on from my prior patch that switches to using
GetSystemTimeAs
There's the chance of interactions that can't occur if each SDK is used
in isolation on its own machine, but it should be pretty minimal.
I have a machine that currently does this with Jenkins. I'll look at
bringing up buildfarm members on it. It's win2k8 though.
--
Craig Ringer
.and violates the
usual expectations about which clauses can have filtering effects.
So the read-filtering policy should apply to all statements. Not just
SELECT.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Se
On 10/16/2014 01:44 PM, Craig Ringer wrote:
> So the read-filtering policy should apply to all statements. Not just
> SELECT.
Oh, IIRC one wrinkle in the prior discussion about this was that doing
this will prevent the implementation of policies that permit users to
update/delete rows they
You'd also want to flag this connection so it's ignored by the smart
shutdown check, allowing the server to shut down even if it's active.
That'd be a pretty useful thing to have anyway, so monitoring tools,
long-running reports that can be restarted ,etc can mark their
connec
On 08/10/2014 07:48 PM, Craig Ringer wrote:
> Hi all
>
> I just had an idea I wanted to run by you all before turning it into a
> patch.
>
> People seem to get confused when they get auth errors because they
> changed pg_hba.conf but didn't reload.
>
> Should w
s.
I'm less sure that this is a worthwhile improvement than the check for
PGDMP and custom format dumps though.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
>From e3a6633ec2782264f3a87fbe3be079f94d89b91
more rows than it reports a
resultset for. As well as being potentially dangerous for people using
it in wCTEs, etc, to me that's the most astonishing possible outcome of all.
I'd be much happier with even:
ERROR: RETURNING not permitted with SELECT row-security policy
than this.
error rates and relatively low disk failure rates. I
personally tend to consider two parity disks the minimum acceptable for
arrays of more than four or five disks. I'd certainly want continuous
archiving or streaming replication in place if I was running RAID 50 on
a big array.
--
Craig Rin
> Whereas if I add a quick hack into init_win32_gettimeofday() so that it
> always chooses GetSystemTimeAsFileTime() I see:
>
> test=# select current_timestamp;
> NOTICE: 9953
> NOTICE: GetSystemTimeAsFileTime
I'll publish the test code I was using too. I was doing it fro
Here's an updated patch addressing David's points.
I haven't had a chance to test it yet, on win2k8 or win2k12 due to
pgconf.eu .
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training &
trouble.
That's probably not really worth it; it's completey different to what
the prior code was doing anyway.
> Also if you decide to get rid of the elog, probably should also remove
> the include of elog.h that you've added.
Rather.
--
Craig Ringer http
y for the
user to suppress that, and it'll be emitted for each backend start.
Though on the other hand it really is a "shouldn't happen" case.
So the options seem to be ignoring the error silently or printing to stderr.
--
Craig Ringer http://www.2ndQuadr
seen this often enough:
postgres=> createdb test
postgres->
postgres->
and it should be solveable with the same approach I used for PGDMP.
It's only a couple of hours work at most but I'm not going to get to it
in a hurry, so let's pop it on the TODO for v
ormally see it, but it'd make it easier to trace what's going
on if you ask for it.
IMO doing this would give us the most important benefits of a proper
authentication negotiation handshake with fallback - without requiring
protocol changes.
It doesn't let you do fancier stuff li
On 10/29/2014 10:45 AM, Tom Lane wrote:
> Craig Ringer writes:
>> At pgconf-eu Álvaro and I were discussing the idea of allowing 'peer'
>> and 'ident' authentication to fall back to md5 if the peer/ident check
>> failed.
>
> I think it would be
er/ident before falling back to something else.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
not be used.
>
> I wonder whether there's a better way to solve this problem.
> Any help will be appreciated.
>
> Best Regards
> Rohtodeveloper
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training &
(assuming we limit it to rather
> simple use cases only)?
Client/server pipleline deadlocks due to how PgJDBC manages it.
See the details:
https://github.com/pgjdbc/pgjdbc/issues/195
and
https://github.com/pgjdbc/pgjdbc/issues/194
--
Craig Ringer http://www.2ndQuadrant.
though, and may be a significant performance _loss_ if you're sending
big queries but getting small replies.
For JDBC the JDBC batch interface is the right place to do this, and you
should not IMO attempt to add pipelining outside that interface.
(Multiple open resultsets from portals
that, but
nothing in the spec:
https://jcp.org/aboutJava/communityprocess/mrel/jsr221/index.html
seems to stop us doing it.
The batch interface doesn't offer any way to set scrollable/editable
resultset options, but we don't want to allow that for batches anyway.
--
Craig Ring
ntarray?
I'm aware of issues with the rest (and I think citext has a few of its
own too) but I didn't think intarray had any real issues.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-ha
, when we already have batching?
Just use the standard JDBC API batching facilities and add the missing
support for batching queries that return result sets in PgJDBC.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
S
mode makes
a lot of sense. The biggest problem is exception handling - you can't
throw an exception at some statement execution in the past. So you need
a new interface for piplelining... or to just use the existing batch
interface.
--
Craig Ringer http://www.2ndQuadrant
nnection.consumeInput() so apps can call that in their
main loops, or via a helper thread. Then we'd be able to add async
notification callbacks too. To do that we need to make PGstream use a
java.nio.Channel instead of a java.net.socket .
--
Craig Ringer http://www.2n
h batches. Though I still
think you're going to have to fix the buffer management code before you
do anything like this.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list
ET SESSION
CHARACTERISTICS isolation mode of serializable. Note that SET
TRANSACTION is SQL-standard.
AFAIK deferring the snapshot that's consistent with other RDBMSes that
use snapshots, too.
The docs of that command allude to, but doesn't explicitly state, the
behaviour you mentio
1101 - 1200 of 2076 matches
Mail list logo
