eprecation notice.
I don't know how many (how few?) add pg_legacytimestamp to USE when
merging postgresql. But it is still available as of 9.6 and also
with their live build of git://git.postgresql.org/git/postgresql.git.
-JimC
--
James Cloos OpenPGP: 0x997A9F17ED7DAEA6
--
S
of the current rules?
Cheers,
James Sewell,
PostgreSQL Team Lead / Solutions Architect
Suite 112, Jones Bay Wharf, 26-32 Pirrama Road, Pyrmont NSW 2009
*P *(+61) 2 8099 9000 <(+61)%202%208099%209000> *W* www.jirotech.com *F *
(+61) 2 8099 9099 <(+61)%202%2
On 15/07/2016 09:28, Craig Ringer wrote:
I don't think anyone's considering moving from multi-processing to
multi-threading in PostgreSQL. I really, really like the protection
that the shared-nothing-by-default process model gives us, among other
things.
As I understand it, the main issue is
; Services
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
> )
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
--
James Sewell,
PostgreSQL Team Lead / Solutions Architect
OK cool, thanks.
Can we remove the minimum size limit when the per table degree setting is
applied?
This would help for tables with 2 - 1000 pages combined with a high CPU
cost aggregate.
Cheers,
James Sewell,
PostgreSQL Team Lead / Solutions Architect
ntly this patch will not fire on small tables even when
parallel_degree is set, can we fix this by adding a check for
ref->parallel_degree to the table size condition?
Cheers,
James
--
--
The contents of this email are confidential and may be subject to legal or
QUERY PLAN
---
GroupAggregate (cost=0.56..600085.92 rows=31 width=16)
Group Key: view_time_day
-> Index Only Scan using base_view_time_day_count_i_idx on base
(cost=0.56..450085.61 rows=3000 width=12)
(3 rows)
Cheers,
Jam
stand though. If
I run parallel agg on a table with 4 rows with 2 workers will it run on two
workers (2 rows each) or will the first one grab all 4 rows?
Cheers,
James Sewell,
PostgreSQL Team Lead / Solutions Architect
__
Level 2, 50 Queen St, Melbourne VIC
o the the threshold multiplier
(currently hard coded to 3) per table - but this might become pretty hard
to explain succinctly in the documentation.
Cheers,
James
--
--
The contents of this email are confidential and may be subject to legal or
professional privilege
x27;t seem to get a parallel
plan for a tiny table. Any idea on why this would be David?
Cheers,
James Sewell,
PostgreSQL Team Lead / Solutions Architect
__
Level 2, 50 Queen St, Melbourne VIC 3000
*P *(+61) 3 8370 8000 *W* www.lisasoft.com *
On Tue, Mar 15, 2016 at 9:32 AM, Robert Haas wrote:
>
> I kind of doubt this would work well, but somebody could write a patch
> for it and try it out.
OK I'll give this a go today and report back.
Would the eventual plan be to use pg_proc.procost for the functions from
each aggregate concerne
On Tuesday, 15 March 2016, Robert Haas wrote:
>
> > Does the cost of the aggregate function come into this calculation at
> > all? In PostGIS land, much smaller numbers of rows can generate loads
> > that would be effective to parallelize (worker time much >> than
> > startup cost).
>
> Unfortunat
r for testing, set the work_mem higher.
>
>
Ah, that makes sense.
Tried with a BTREE index, and it works as perfectly but the index is 428MB
- which is a bit rough.
Removed that and put on a BRIN index, same result for 48kB - perfect!
Thanks for the help,
James
--
-
he workers, but it currently isn't.
*/
Does this mean that even though we are aggregating in parallel, we are only
operating on one child table at a time currently?
Cheers,
James Sewell,
Solutions Architect
__
Level 2, 50 Queen St, Melbourne VIC 30
27;DAY'::text, ts))
-> Seq Scan on a (cost=0.00..397059.30 rows=2024 width=12)
(5 rows)
Unsure what's happening here.
James Sewell,
PostgreSQL Team Lead / Solutions Architect
__
Level 2, 50 Queen St, Melbourne VIC 3000
*P *(+61) 3 83
Group Key: date_trunc('DAY'::text, pageview_start_tstamp)
-> Parallel Seq Scan on celebrus_fact_agg_1_p2015_12
(cost=0.00..743769.76 rows=4221741 width=12) (actual time=0.066..1631
.650 rows=3618887 loops=7)
One question - how is the upper limit of workers chos
2278.449 ms
6 2000.599 ms
I'm pretty happy!
Cheers,
James Sewell,
PostgreSQL Team Lead / Solutions Architect
__
Level 2, 50 Queen St, Melbourne VIC 3000
*P *(+61) 3 8370 8000 *W* ww
Argh seems like a false alarm for now.
I installed 9.5 from RPM source (the other was one I had installed
previously) and the performance matched 9.6
Sorry about that, I must have *something* screwed up on the other one.
Cheers,
James Sewell,
PostgreSQL Team Lead / Solutions Architect
I've actually just tested this on 9.3 - and I get roughly the same as
9.6devel.
Now going back to make sure my 9.5 environment is sane.
Hopefully this isn't me jumping the gun.
Cheers,
James Sewell,
PostgreSQL Team Lead / Solutions Architect
__
both nodes:
HashAggregate (cost=670590.56..670590.95 rows=31 width=13)
Group Key: view_time_day
-> Seq Scan on base (cost=0.00..520590.04 rows=3104 width=13)
Cheers,
James Sewell,
PostgreSQL Team Lead / Solutions Architect
__
Level 2, 50 Que
On 27/01/2016 13:30, Amit Kapila wrote:
Thoughts?
Are the decreases observed with SSD as well as spinning rust?
I might imagine that decreasing the wear would be advantageous,
especially if the performance decrease is less with low read latency.
--
Sent via pgsql-hackers mailing list (p
ads only)
- DR (replica with no reads or writes - until it becomes a master)
Keen to hear comments.
Cheers,
James Sewell,
Solutions Architect
__
Level 2, 50 Queen St, Melbourne VIC 3000
*P *(+61) 3 8370 8000 *W* www.lisasoft.com *
ceil(3), Down as floor(3).)
-JimC
--
James Cloos OpenPGP: 0x997A9F17ED7DAEA6
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
, and they are in a partition layout so it really hurts when I
do the min call on the parent table.
Cheers,
James Sewell,
PostgreSQL Team Lead / Solutions Architect
__
Level 2, 50 Queen St, Melbourne VIC 3000
*P *(+61) 3 8370 8000 *W* www.lisaso
Oh,
I've just noticed something in the Commit fest post
- Reducing lock strength of trigger and foreign key DDL
Perhaps I just need to be more patient.
Cheers,
James Sewell,
Solutions Architect
__
Level 2, 50 Queen St, Melbourne VIC 3000
*P *(+
I missing some edge case
when this lock would be required in this circumstance?
No real urgency on this question, I just found it a bit strange and thought
someone might be able to shed some light.
James Sewell,
Solutions Architect
__
Level 2, 50 Queen St
On 03/10/2014 05:53, Kouhei Kaigai wrote:
> Yep, that's my pain. Even though usual query does not take many buffers
> pinned,
> my use case needs to fetch megabytes scale data at once because of performance
> reason; page-by-page synchronous scan makes GPU being idle.
Doesn't your GPU have an asyn
ns of glibc where doing certain math on double is
faster than doing it on float, depending on how things are compiled.
Maybe this is one of them?
-JimC
--
James Cloos OpenPGP: 0x997A9F17ED7DAEA6
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On 02/03/2014 15:30, Magnus Hagander wrote:
Terminal Services have definitely become more common over time, but
with faster and cheaper virtualization, a lot of people have switched
to that instead, which would remove the problem of course.
I wonder how common it actually is, though, to *build
Node A could get ahead even if it has been shut down cleanly BEFORE the
promotion?
I'd always assumed if I shut down the master the slave would be at the same
point after shutdown - is this incorrect?
Cheers,
James Sewell,
PostgreSQL Team Lead / Solutions Arch
doesn't cover a crash), can
anyone see any potential problems with this approach?
Cheers,
James Sewell,
PostgreSQL Team Lead / Solutions Architect
__
Level 2, 50 Queen St, Melbourne VIC 3000
*P *(+61) 3 8370 8000 *W* www.lisasoft.com *F *(+61) 3 8370 8
ostgresql.org/message-id/519df910.4020...@vmware.com
Cheers,
James Sewell,
PostgreSQL Team Lead / Solutions Architect
__
Level 2, 50 Queen St, Melbourne VIC 3000
*P *(+61) 3 8370 8000 *W* www.lisasoft.com *F *(+61) 3 8370 8099
--
-
On Tue, 2014-01-14 at 15:09 -0500, Robert Haas wrote:
> On Tue, Jan 14, 2014 at 3:00 PM, James Bottomley
> wrote:
> >> Doesn't sound exactly like what I had in mind. What I was suggesting
> >> is an analogue of read() that, if it reads full pages of data to a
>
On Tue, 2014-01-14 at 12:39 -0500, Robert Haas wrote:
> On Tue, Jan 14, 2014 at 12:20 PM, James Bottomley
> wrote:
> > On Tue, 2014-01-14 at 15:15 -0200, Claudio Freire wrote:
> >> On Tue, Jan 14, 2014 at 2:12 PM, Robert Haas wrote:
> >> > In terms of avoiding do
On Tue, 2014-01-14 at 10:39 -0500, Tom Lane wrote:
> James Bottomley writes:
> > The current mechanism for coherency between a userspace cache and the
> > in-kernel page cache is mmap ... that's the only way you get the same
> > page in both currently.
>
> Rig
it). Then at some time later, you want to designate it as written back
to the file instead so you control the writeout order. I'm not sure we
can do this: the separation between file backed and anonymous pages is
pretty deeply ingrained into the OS, but if it were possible, i
On Tue, 2014-01-14 at 11:48 -0500, Robert Haas wrote:
> On Tue, Jan 14, 2014 at 11:44 AM, James Bottomley
> wrote:
> > No, I'm sorry, that's never going to be possible. No user space
> > application has all the facts. If we give you an interface to force
> > un
yond what normal
> write can do.
The problem is we can't give you absolute control of when pages are
written back because that interface can be used to DoS the system: once
we get too many dirty uncleanable pages, we'll thrash looking for memory
and the system will livelock.
James
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
k ever.
>
> I don’t understand. Are we talking about mmap()ed files here? Why
> would the kernel be trying to write back pages that aren’t dirty?
No ... if I have it right, it's pretty awful: they want to do a read of
a file into a user provided buffer, thus obtaining a page cache entry
and a copy in their userspace buffer, then insert the page of the user
buffer back into the page cache as the page cache page ... that's right,
isn't it postgress people?
Effectively you end up with buffered read/write that's also mapped into
the page cache. It's a pretty awful way to hack around mmap.
James
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
c.
>
> Reimplementing i/o schedulers and all the rest of the work that the
> kernel provides inside Postgres just seems like something outside our
> competency and that none of us is really excited about doing.
This would also be a well trodden path ... I believe that some large
databa
On Mon, 2014-01-13 at 22:12 +0100, Andres Freund wrote:
> On 2014-01-13 12:34:35 -0800, James Bottomley wrote:
> > On Mon, 2014-01-13 at 14:32 -0600, Jim Nasby wrote:
> > > Well, if we were to collaborate with the kernel community on this then
> > > presumably we
uring out what policy to use. Remember,
> > you cannot tell the kernel to put some page in its page cache without
> > reading it or writing it. So, once you make the kernel forget a page,
> > evicting it from shared buffers becomes quite expensive.
>
> Well, if we were t
On 06/01/2014 04:20, Amit Kapila wrote:
Duplicate handle should work, but we need to communicate the handle
to other process using IPC.
Only if the other process needs to use it. The IPC is not to transfer
the handle to
the other process, just to tell it which slot in its handle table
contains
On 06/01/2014 03:14, Robert Haas wrote:
That's up to the application. After calling dsm_create(), you call
dsm_segment_handle() to get the 32-bit integer handle for that
segment. Then you have to get that to the other process(es) somehow.
If you're trying to share a handle with a background wor
On 05/01/2014 18:02, Robert Haas wrote:
On Sun, Jan 5, 2014 at 12:34 PM, james wrote:
>On 05/01/2014 16:50, Robert Haas wrote:
>
> But on Windows, segments are*automatically*
>destroyed*by the operating system* when the last process unmaps them,
>so it's not quite so cl
On 05/01/2014 16:50, Robert Haas wrote:
But on Windows, segments are*automatically*
destroyed*by the operating system* when the last process unmaps them,
so it's not quite so clear to me how we can allow it there. The main
shared memory segment is no problem because the postmaster always has
useful
for some. And RC4, perhaps, also should be !ed.
And if anyone wants Kerberos tls-authentication, one could add
KRB5-DES-CBC3-SHA, but that is ssl3-only.
Once salsa20-poly1305 lands in openssl, that should be added to the
start of the list.
-JimC
--
James Cloos OpenPGP: 1
am happy
throw an error (although this doesn't seem to be how option such as LDAPTLS
work: 1 if 1 else 0). I assume I would use the ereport() function to do
this (using the second example from this page
http://www.postgresql.org/docs/9.2/static/error-message-reporting.html)?
Cheers,
James
I was avoiding ON_ERROR_STOP because I was using ON_ERROR_ROLLBACK, but
have just realised that if I encase my SQL in a transaction then rollback
will still happen.
Perfect!
James Sewell,
PostgreSQL Team Lead / Solutions Architect
__
Level 2, 50 Queen St
Hello,
I am using PSQL to run SQL from a file with the -f flag as follows:
BEGIN
SQL
SQL
...
END
This gives me rollback on error and a nicer output than -1. This works fine.
My question is in a rollback scenario is it possible to get PSQL to return
a non 0 exit status?
Cheers,a
James
d"
CREATE TABLE
postgres=# alter table test1 owner to postgres;
ALTER TABLE
Cheers,
James Sewell
Solutions Architect
_
[image:
http://www.lisasoft.com/sites/lisasoft/files/u1/2013hieghtslogan_0.png]
Level 2, 50 Queen St,
Melbourne, VIC, 3000
P: 03 8370 8000
On 14/07/2013 20:13, Greg Smith wrote:
The most efficient way to write things out is to delay those writes as
long as possible.
That doesn't smell right to me. It might be that delaying allows more
combining and allows the kernel to see more at once and optimise it, but
I think the counter-a
Hey,
New patch attached. I've moved from using a boolean to an enum trivalue.
Let me know what you think.
Cheers,
James
James Sewell
PostgreSQL Team Lead / Solutions Architect
_
[image:
http://www.lisasoft.com/sites/lisasoft/files/u1/2013hieghtslogan_
ferral chasing
The other option would be to have the default value (of the parameter) be
true and set the boolean to false to disable it. I can't find any other
examples of this though - I assume having a one off like this in the code
is a bad thing also?
I'm happy to let you guys d
ith
the library defaults? To 'enable' the new behavior here using a boolean you
would need to set ldapreferrals=false - which with the normal way of
dealing with config booleans would alter the default behavior if the option
was not specified.
How do you feel about:
ldapdisablerefer
this setting seems to be the default for
ldapsearch on Linux these days.
Hopefully I found all the documentation that I was meant to update, let me
know if not though.
Cheers,
James Sewell
PostgreSQL Team Lead / Solutions Architect
_
[image:
http://www.lisasoft
On 01/07/2013 02:43, Claudio Freire wrote:
In essence, you'd have to use another implementation. CPython guys
have left it very clear they don't intend to "fix" that, as they don't
consider it a bug. It's just how it is.
Given how useful it is to have a scripting language that can be used outsid
On 25/06/2013 05:16, Tom Lane wrote:
It might be time to reconsider whether we should move the baseline
portability requirement up to C99.
My understanding was that you picked up a lot of users when the Win32
port became useful. While you can build with msys, I would think that
leaving Micro
> Have you considered GPU-based sorting? I know there's been discussion
in the past.
If you use OpenCL, then you can use a CPU driver if there is no GPU, and
that can allow you to leverage all the CPU cores without having to do
the multi-thread stuff in the backend.
While the compilation of
hexidecimal notation for floats exists. The printf format flag is %a
for miniscule and %A for majuscule.
The result of 1./3. is 0xa.aabp-5.
This site has some info and a conversion demo:
http://gregstoll.dyndns.org/~gregstoll/floattohex/
-JimC
--
James Cloos OpenPGP: 1024D/E
On the contrary, only a few months ago there was a far from groundless fear
that Microsoft would do just that. Following considerable outcry they changed
their mind. But this is definitely not just paranoia. As for w64 support, the
mingw-64 project exists more or less explicitly to produce 64 b
Anyway, this is getting way off track. The point is that the MS SDKs and
compilers are a bit of a mess and that MinGW support is useful because
we can't rely on them continuing to offer free SDKs and compilers in future.
Well, more compilers are always useful, but complaining that Microsoft
mig
So, while no native 64-bit compilers are available for free as part of
Visual Studio Express 2012 (11), it doesn't matter much. The issue is
more that it's very much Microsoft's whim whether they release compilers
at all and if so, which ones, when and how.
I think I have a pretty vanilla Visual
You can use COPY from a stored procedure, but only to and from files.
I think that's in the chocolate fireguard realm though as far as
efficiency for this sort of scenario goes, even if its handled by
retaining an mmap'd file as workspace.
If SPI provided a way to perform a copy to a temp
27;m trying to limit manipulations to one
statement per table per logical operation even where there are multiple
detail rows.
Sometimes the network latency can be a pain too and that also suggests
an RPC with unpack and insert locally.
Cheers
James
--
Sent via pgsql-hackers mailing
The processing functions have been extended to provide populate_record() and
populate_recordset() functions.The latter in particular could be useful in
decomposing a piece of json representing an array of flat objects (a fairly
common pattern) into a set of Postgres records in a single pass.
note about adding explicit mention to the docs was expressly
because it is not otherwise obvious whether indices should use lower()
or upper().
I'll ask on one of the unicode lists whether there are any locales where
a case-insensitive match should be different than a case-preserving match
of
R(column) to benefit ILIKE?
Perhaps the parser could read the former as the latter?
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
quire significant surgery.
Is there any way to specify the index such that the ILIKE query will use
said index?
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
mb table has several indices, including separate ones on name and ownerid.
(not my design, btw. And I really do need to re-write the middleware)
Whether it is strcoll(3) (even though LC_COLLATE is explicitly C) or
LIKE, it does make a significant difference for those two apps.
-JimC
now sets LC_CTYPE. Would that explain why lc_ctype
changed between the two clusters?
Is there any way to alter a db's lc_ctype w/o dumping and restoring? I
want to preserve some of the changes made since I copied the 9.1 cluster.
Alter database reports that lc_ctype cannot be changed.
-Jim
Its a Gentoo box; both were build from their ebuilds, with the same gcc,
flags, etc.
PE> Compare the output of pg_config --configure from both installations.
The only differences are 9.1 vs 9.2 in the paths.
Thanks,
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
Sent via
>>>>> "AF" == Andres Freund writes:
AF> Is it possible that you compiled with assertions enabled? That would
roughly
AF> fit that magnitude. SHOW debug_assertions; Should show you whether it was
AF> enabled.
Thanks, but SHOW debug_assertions r
at the plans are the same suggests that isn't
the problem, yes?
I think I recall mention from a previous beta (but goog isn't helping me
confirm) that there is some extra debugging or such enabled in the betas.
If so, and if turning that off would provide a better comparison, where
in the
impacted tables and for each table a list of affected primary keys and
whether they were inserted, deleted or updated.
James
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
impacted tables and for each table a list of affected primary keys and
whether they were inserted, deleted or updated.
James
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
How easy would it be to implement a fake async rep target?
Perhaps even as something that a server could allow a connection to
request? (ie a suitably permissioned connection could convert itself to
receive n async replication stream, rather than being statically
configured?)
I know that it
That is, if you request FD_WRITE events for a pre-existing socket with
WSAEventSelect, you will not get one until the outbound network buffer has
been filled and then has partially emptied. (This is incredibly broken,
but Microsoft evidently has no intention of fixing it.)
I think you should di
I believe there are tools that are significantly faster than flex. I
believe re2c generates code that is faster. But the key thing is to
test, probably, or perhaps ask around. I'm out of touch, but from
memory flex wasn't the be-all and end-all.
Lemon is definitely easy to maintain/port and
Doesn't that imply that a plan cache might be worthwhile?
But no matter: didn't the OP really have issue with packaging and
Windows support - and there are a lot of Windows users, and in general
there are many Windows devs: making it easier for them to contribute has
to be good doesn't it?
-
r let the parser drive a pull
loop, or use a coroutine structure.
Could go all trendy and use a PEG tool like, er,, peg
(http://piumarta.com/software/peg/). (I haven't tried them tho')
James
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to yo
ragonfly's swapcache seems to me remarkably elegant and, it would seem,
very effective.
James
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
their work.
But it little bit digging in the mailing list archives should turn
them up.
Many thanks, Florian, we'll be checking that out.
James
James Robinson
Socialserve.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscrip
anting to go over to plpythonu or whatnot (whose description
of rows are as dicts).
Is there something in the internals which inherently prevent this? Or
am I fool and it already exists?
Not having to defer to EXECUTE would be attractive.
James Robinson
Socialserve.com
--
Sent via pgsql-hacker
On Mar 1, 2011, at 12:10 PM, Jan Urbański wrote:
> So you end up with a context message saying "PL/Python function %s" and
> a detail message with the saved detail (if it's present) *and* the
> traceback. The problem is that the name of the function is already in
> the traceback, so there's no need
On Dec 23, 2010, at 3:38 AM, Jan Urbański wrote:
> Oh, didn't know that. I see that it does some more fancy things, like
> defining a inheritance hierarchy for these exceptions and adding some
> more into the mix.
Right, there were some cases that appeared to benefit from larger
buckets than what
On Dec 13, 2010, at 6:16 PM, Tom Lane wrote:
> how do you identify which type OID is really hstore?
How about an identification field on pg_type?
CREATE TYPE hstore ..., IDENTIFIER 'org.postgresql.hstore';
-- Where the "identifier" is an arbitrary string.
Type information can be looked up by th
only writing 8k blocks then there is probably little hope of
making efficient use of flash.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
sd for pg_xlog and the journals for the other
filesystems, but they cost too much.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ould such a patch for master be rejected?
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
that the float timestamps were archaic; that avoids any
need of %A for timestamps.
That said, the possiblity of hex i/o format for the float datatypes
would be welcome.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.or
>>>>> "JD" == Jeff Davis writes:
JD> 2. Fix the input/output functions in a special mode for dump/reload,
JD>to make them true inverses.
That can be done by supporting the %A printf(3)/scanf(3) format.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DA
ding git
describe's dirty designation is important when using it in that
fashion. But it helps to be able to run git add --all cleanly.
I understand that other git users have similar experience.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
Sent via pgsql-hackers mailing list (
sable to do this via multiple clusters
instead of a single cluster, tweaking the processor affinity of each
postmaster accordingly, trying to ensure each cluster's shared memory
segments and buffer cache pools remain local for the resulting backends?
Thanks!
James Robinson
Soci
On Aug 9, 2010, at 11:49 AM, Kris Jurka wrote:
> Oh, duh. It's a server side copy not going through the client at all. Here's
> a hopefully final patch.
Trying it out... Works for me.
I understand the resistance to the patch, but it would be
quite nice to see this wart in the rear view. =\
--
On Aug 14, 2010, at 9:08 AM, Tom Lane wrote:
> Just to clarify, you're recommending something like
>
> proc->me = PyCObject_FromVoidPtr(proc, NULL);
> + if (proc->me == NULL)
> + elog(ERROR, "could not create PyCObject for function");
> P
On Aug 13, 2010, at 5:20 PM, Tom Lane wrote:
> According to a discussion over in Fedora-land, $subject is true:
> http://lists.fedoraproject.org/pipermail/devel/2010-August/140995.html
>
> I see several calls in plpython.c that seem to refer to PyCObject stuff.
> Anybody have any idea if we need t
On Aug 6, 2010, at 4:31 PM, Kris Jurka wrote:
>
I think there's a snag in the patch:
postgres=# COPY data FROM '/Users/jwp/DATA.bcopy' WITH BINARY;
ERROR: row field count is -1, expected 1
CONTEXT: COPY data, line 4
Probably a quick/small fix away, I imagine.
But, I was able to trigger the
On Jul 28, 2010, at 9:53 AM, Kris Jurka wrote:
> Technically you won't get NotificationResponse until transaction end, so you
> don't need to worry about that mid copy.
Ah, thanks for noting that. It would appear my original reading of the async
section didn't get far enough beyond "Frontends mu
On Jul 25, 2010, at 8:01 AM, Kris Jurka wrote:
> The JDBC driver reads server messages for multiple reasons.
> One of them is indeed to do early failure detection.
That's high quality. =)
> Another is to pickup NoticeResponse messages to avoid a network buffer
> deadlock.
That's a good catch.
1 - 100 of 359 matches
Mail list logo
