, but I think what you
really want is a named pipe.
I don't see any reason in principle to disallow use of a named pipe as a
password file. It could be a bit of a footgun, though, since writing to
the fifo would block until it was opened by the client, so you'd need to
be very careful
Author: Bruce Momjian
> Date: Fri Jun 10 03:02:30 2005 +
>
> Add the "PGPASSFILE" environment variable to specify to the password
> file.
>
> Andrew Dunstan
>
> and poking around in the mailing list archives from th
ay up, but nothing is
telling me what setting is the problem, Is there any way I can figure out
what specific watchdog setting its complaining about?
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
fire
and all those other tables need to be updated too.
> However, if that fails, the table is dead. You will have to reload it from
> backup.
Right, and that goes for all the affected tables.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing l
schemas in sync during
cutover period).
This second approach isn't faster, it's hard on I/O and disk space,
but it keeps you up and you can do the changes at a leisurely pace.
Just make sure you have the I/O and space before you do it :)
Hope that helps,
A
--
Andrew Sullivan
a...@crankyca
Possamai
wrote:
>
>
> 2017-06-12 9:52 GMT+12:00 Andrew Kerber :
>
>> Was that transparent hugepages or standard hugepages? databases commonly
>> have problems dealing with transparent hugepages.
>>
>>
>
>
> IN my case, it was the Transparent Hugepages..
Was that transparent hugepages or standard hugepages? databases commonly
have problems dealing with transparent hugepages.
On Sun, Jun 11, 2017 at 4:39 PM, Lucas Possamai
wrote:
> 2017-06-12 7:52 GMT+12:00 Andrew Kerber :
>
>> I am sure it does not.
>>
>> Sent from my
I am sure it does not.
Sent from my iPhone
> On Jun 11, 2017, at 10:50 AM, pinker wrote:
>
> Andrew Kerber wrote
>> I can't give you an absolutely authoritative answer, but because of the
>> way hugepages are implemented and allocated, I can't think how
I can't give you an absolutely authoritative answer, but because of the way
hugepages are implemented and allocated, I can't think how they could be used
for other processes. Linux hugepages are either 2m or 1g, far too large for
any likely processes to require. They cannot be allocated in part
e action to show that interleave but there is an
> underlying race condition since both BT1 and BT2 are executing concurrently.
>
> In short even with IF NOT EXISTS you are not guaranteed to not fail. But
> at least IF NOT EXISTS makes the probability of not failing > 0. It
> doesn't handle the concurrency any better - but it does change the outcome
> in some of those less-than-ideally handled situations.
>
> David J.
>
>
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
Hi Paul,
How much of your data is time-series in nature? Put another way, is there a
timestamp coupled with the inserted data?
Andrew
On Fri, May 12, 2017 at 4:38 PM, Ivan E. Panchenko <
i.panche...@postgrespro.ru> wrote:
> Hi
>
>
> 12.05.2017 23:22, Justin Pryzby пишет:
&
Yes, that was the first item on my list (disk space)...
On Fri, Apr 28, 2017 at 11:56 AM, Scott Marlowe
wrote:
> On Fri, Apr 28, 2017 at 8:39 AM, Andrew Kerber
> wrote:
> > I am a fairly experienced Oracle DBA, and we are starting to move in to
> the
> > PostgreSQL world
a transaction even without any Insert/update/delete command, so I
had to explain that to my developers.
On Fri, Apr 28, 2017 at 11:04 AM, John R Pierce wrote:
> On 4/28/2017 7:39 AM, Andrew Kerber wrote:
>
>> I am a fairly experienced Oracle DBA, and we are starting to move
correct port, CPU usage.
Are there additional PostgreSQL specific items that need to be monitored?
if so, what items?
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
) but also because outsiders will often point
> out previous poor work to the boss, often with no understanding of the
> historical reasons behind it.
>
> Trying to change people's attitudes, unless you're explicitly brought in
> with that brief, is likely to provoke exactly tha
blogged yesterday about TimescaleDB's partitioning design choices in
more depth, if you are interested:
https://blog.timescale.com/time-series-data-why-and-how-to-u
se-a-relational-database-instead-of-nosql-d0cd6975e87c
On Thu, Apr 20, 2017 at 5:43 PM, Samuel Williams <
space.ship.tr
Awesome thread.
Samuel,
Just wanted you to be aware of the work we're doing at TimescaleDB (
http://www.timescale.com/), a time-series database extension for PostgreSQL.
Some of how we might help you:
- automatic partitioning by space (primary key - like country_id, for
instance) and time. This
ion of some of the key contributors to Postgres, who
appear to work mostly in a mode where email makes things easy for them
and logging into a new forum tool makes things harder.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postg
al one -- that requires no trades.
Distributing data reliably with ACID semantics and no data loss or
corruption or loss in write throughput is not possible, at least
today. You have to pick which poison you want :)
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general m
Oh, I can answer that. The owner of the postgreSQL executable must have
the privilege to lock pages in memory.
On Tue, Jan 17, 2017 at 9:38 AM, Tom Lane wrote:
> Andrew Kerber writes:
> > Does PostgreSQL 9.4 support large pages in windows? The setting is there
> > in the postg
Thats what I needed, thank you. Windows generally calls them large pages,
AIX also calls them large pages, really they are typically only called
hugepages on Linux.
On Tue, Jan 17, 2017 at 9:28 AM, Adrian Klaver
wrote:
> On 01/17/2017 07:20 AM, Andrew Kerber wrote:
>
>> Does Po
Does PostgreSQL 9.4 support large pages in windows? The setting is there
in the postgresql.conf, but I cant tell if it is supported in windows?
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
Cutting ties by my own interest: I want better Postgres. I want to teach
those who probably will push patches.
Best regards, Andrey Borodin.
четверг, 6 октября 2016 г. пользователь Joshua D. Drake написал:
> On 10/06/2016 10:39 AM, Andrew Borodin wrote:
>
>> Hi everyone!
>>
&g
Hi everyone!
From time to time I teach at Ural Federal University. Currently
university wants me to make up online course. They are going to put it
to platform like edX or something.
I do not want to do another general programming course, so I made up
my mind to do a “postgres-hacker” course. But
to some other
place later, and it'd suck if the transaction failed half way through
because it turns out there's nowhere to put the data I've just staged.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
dd to
get the next logical row number; the "x" table actually computes the
logical row number; finally we group by the logical row number and use
string_agg to get a single name for each row.
Is there an easier way to write this query, using some window function
functionality that I
ason we're still using 9.2.
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
m. But one has to
face the critique in its own terms.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
mpatibility historically was the basis for something
becoming a major version upgrade. (I can recall a couple bugs where
you had to tickle the catalogues, so it's not exactly true that
they're never incompatible, but it's incredibly rare.)
Best regards,
A
--
Andrew Sullivan
a...@crankycanu
27;t deserve while
> they treat customers and employees with similar levels of arrogance.
Nothin' for nothin', but I don't think it helps Postgres to attack
others' business plans -- whatever one thinks of them -- as part of an
argument about why Postgres is the right tool fo
function signature be?
Thanks
Andrew
[1] https://www.postgresql.org/docs/9.5/static/xindex.html
this mysql2pgsql conversion rather than N dedicated small teams for
> every mysql client out there.
…I don't think anyone is telling you, "Don't build this." You should
do what you like with your time :)
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailin
s to MySQL, MySQL always wins, what you teach them is
"Postgres performance sucks."
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
So, I am a decent oracle SQL and PL/SQL programmer looking to expand into
PostgreSQL. Can someone point me to a decent programming book on the
topic? I have looked Amazon and Apress and not found much, so I am not
sure where to turn. Or perhaps I am looking the wrong places.
--
Andrew W
Dear all,
Is there a way to efficiently perform OR conditions across multiple
joins?
For example, I have the following statement:
SELECT RECORD.id
FROM RECORD
left join string
ON string.record_id = RECORD.id
AND string.layout_id = 6
left join DATE
On Sat, 4 Jun 2016 Andrew Beverley wrote:
> I'm performing a query with many joins, with a WHERE condition on the
> "root" table. As far as I am aware, each join is indexed, as is the
> WHERE clause. To my simple mind, this is just a case of taking a set
> of condition
On Sat, 4 Jun 2016 Andrew Beverley wrote:
> When I run EXPLAIN ANALYZE, I see that the actual query is scanning
> significantly more rows for the join than was estimated. There is also
> a huge number of loops for the joins. Why is this, and is there an
> easy fix?
I should have said
Dear all,
I'm performing a query with many joins, with a WHERE condition on the
"root" table. As far as I am aware, each join is indexed, as is the
WHERE clause. To my simple mind, this is just a case of taking a set of
conditional indexed values, and then "adding on" the relevant indexed
data.
W
re's something that we're going to have to accept, however,
and that's that there are way more application coders than there are
people who really get database systems. Fixing this problem requires
years of efforts.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent vi
t I've been in the
sort of long, boring speculative conversation that could have been
shut down quickly with this kind of data.)
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://ww
hors intended. Doesn't matter for
these purposes! :)
[2] Apparently, Marshall McLuhan didn't say this; instead, his tribune
John Culkin, SJ said it. It's still an excellent point, whoever made it.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
card number gets lost in an
eventually-consistent system, and people suddenly understand
viscerally why transactions semantics are so hard.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subs
receive a message that data is committed before any replication of the
data has commenced," would that help?
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
fork. But …
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/postgresql/Driver
… since it can't find the driver, I'd bet that your classpath doesn't
contain /opt/postgresplus/edbmtk/lib.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
he json array to produce a Postgres array
literal. But if we're handling nested composites as well that probably
won't pass muster and we would need to decompose all the objects fully
and reassemble them into Postgres objects. Maybe it won't take as long
as I suspect. If anyone
On 02/24/2016 09:11 AM, David G. Johnston wrote:
On Wednesday, February 24, 2016, Andrew Dunstan <mailto:and...@dunslane.net>> wrote:
Having json(b)_populate_record recursively process nested complex
objects would be a large undertaking. One thing to consider is
that js
s: they are essentially
one-dimensional heterogenous lists, not multi-dimensional homogeneous
matrices. So while a Postgres array that's been converted to a json
array should in principle be convertible back, an arbitrary json array
could easily not be.
cheers
andrew
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
verhead involved in getting
this data into the internal storage format used by PostgreSQL. But even if
I triple the number of bytes stored for each record, I only end up with 51
MB or so. Am I missing something obvious?
Cheers,
Andrew
to recover after a restart.
It may not be the hardware. Depending on how vmware is configured, it
could just be a setting. Also, something in the OP's message made me
think that this was _actually_ a network-attached disk, which can also
have such problems. (But in general, I agree.)
A
at can be done about it?
You may end up taking an outage in effect, because you need to compact
them at least once. If you can flip to a replica, that is the easiest
way to fix it.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.o
at stuff about what the IETF does some
while ago. There is definitely more than one way to do this.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
that you actually want to fail over.
I've seen an awful lot of people want automatic failover who also
can't afford for the already-committed transactions on the master to
be lost. Unless you're running synchronous, be sure you have the
workload that can actually accept lost w
tended in the generic sense. I apologise in case
that wasn't clear.
> It is the perceived intention of what one says that is important, not what
> one actually says!
I think that is perhaps a false dichotomy. But I also think I have
said enough on this topic, so I shall stop now.
B
an we can do something about it by writing down rules.
Still, the exercise of writing down rules may help to notice things
one wouldn't say to a friend. And I hope we're all friends here.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list
children of slaves.
If someone did that, it would fall under (2), no? (I note that a
recent RFC, of which I am a co-author, about DNS terminology did say
that "primary" and "secondary" were to be preferred over "master" and
"slave". I didn't personally
On 1/8/16, 12:51 PM, "Simon Riggs"
mailto:si...@2ndquadrant.com>> wrote:
On 8 January 2016 at 18:56, Joshua D. Drake
mailto:j...@commandprompt.com>> wrote:
On 01/08/2016 10:42 AM, Andrew Biggs (adb) wrote:
Installed 9.5 to CentOS7 via yum, and tried going through the
On 1/8/16, 10:53 AM, Rob Sargent wrote:
On 01/08/2016 10:39 AM, Andrew Biggs (adb) wrote:
Can anyone tell me if PostgreSQL 9.5 supports (either natively or by extension)
the BDR functionality?
I tried it out and ran into issues, but it could well have been I was doing
something wrong.
Thanks
Can anyone tell me if PostgreSQL 9.5 supports (either natively or by extension)
the BDR functionality?
I tried it out and ran into issues, but it could well have been I was doing
something wrong.
Thanks!
Andrew
urage those who think there is a problem to
be solved to make a scratch proposal and see whether it flies. It's
always easier to discuss a concrete proposal than to try to figure out
whether something is a good idea in the abstract. The shorter and
easier to understand the proposal is, I
e the query as a single select and if so how?
Thanks in advance
Andrew Bailey
losing the
shell so that the session hangs around). Eventually, the Postgres
backend will try to talk to the session and discover it isn't there,
and you'll get a termination logged (assuming you have loging turned
up that high).
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent
e you can! There are also some firms that can help with
migration if you like.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
uditor, this might be enough
to satisfy the condition.
Also, of course, there is the application_name (string) parameter. In
principle, you ought to be able to filter on this. Again, won't help
you if your application login is somehow compromised.
I agree that all of this depends on logging
al risk to be
mitigated is. It might, sure. The security profiler would still need
to make a list of this fact and then ask how countermeasures mitigate
it.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresq
metimes people delete data from a system because
it's been archived somewhere else or something like that -- not all
databases have the totality of all the relevant data in them, but can
often represent just "current" data.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
ssibly be exfiltrated,
you need to know the state of all of it.
For realistic cases, I expect that deleted data is usually more
important than updated data. But a threat modeller needs to
understand all these variables anyway.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-g
m MySQL already.
Consistency and rigour are the changes ;-)
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
I. But do consider
trying out the command line. You'll be surprised at the power you get
once the initial learning curve is over.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
h
hacks, but if you need a bugfix prior to a real solution
they'd give you a path.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
lly sure why you think the manual is misleading.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ut you asked what was behind the design
decision and I told you. But in general, the experience seems to be
that triggers are easier to get right (novice or no, _pace_ section
38.7).
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-genera
e all the
data in the table. I don't know what rewriting such a query would
mean.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Tue, 2015-07-21 at 03:00 -0700, John R Pierce wrote:
> On 7/21/2015 1:51 AM, Andrew Beverley wrote:
> > Thanks John. The backup script is running as root, so presumably I'd have
> > to
> > use
> > sudo? Or should I run a separate cron job as postgres to do
On Tue, 2015-07-21 at 01:46 -0700, John R Pierce wrote:
> On 7/21/2015 1:31 AM, Andrew Beverley wrote:
> > I had to specify a database name when connecting:
> >
> > psql -U backup -c "select pg_start_backup('Daily backup')" -d postgres
>
>
On Tue, 2015-07-21 at 16:54 +0900, Michael Paquier wrote:
> On Tue, Jul 21, 2015 at 4:47 PM, Andrew Beverley wrote:
> > Dear all,
> >
> > I'm setting up hot backups on my database server. As such, I'd like to set
> > up a
> > Postgres user
Dear all,
I'm setting up hot backups on my database server. As such, I'd like to set up a
Postgres user that has access to only pg_start_backup and pg_stop_backup.
I'm unable to work out how to do this with the various GRANT options. Can
someone
point me in the right direction please? Or is ther
st, I
found that to be useful when talking to Oracle partisans.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Please do not cross-post on the PostgreSQL lists. Pick the most
appropriate list to post to and just post there.
cheers
andrew
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
emed developer claimed something and
maybe should have relinquished sooner given his workload. That
happens; nobody's perfect. It's frustrating, but this is not the only
community to have had that issue (cf. Linux kernel, for an
approximately infinite series of examples of this). I am not su
onvention.
This case is no different.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ty's time with crowdsourced editing of job
postings is in any way appropriate for the pgsql-general list.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql
b from the
old machine and restore locally, you could do
pg_dump -U postgres -h 192.0.2.1 -C egdb | psql -U postgres
I recommend reading the pg_dump (and if you like, pg_dumpall) manuals
before proceeding.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list
systems to move all the data from one to the
other. Depending on your uptime requirements and the size of the
database, this approach can either be a life saver or a total waste of
time and will to live. More often the latter, please be aware.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sen
Makes sense.
Yes, it would be great if psql offered a flag for validating syntax. Other
programming languages do this, for example, bash -n, ruby -c, and php -l.
On Wed, Apr 8, 2015 at 3:53 PM, Tom Lane wrote:
> Andrew Pennebaker writes:
> > I can't find a relevant section
Could you be more specific?
I can't find a relevant section to address my specific problem: ecpg
complaining when I try to check the syntax of my .sql files that use input
parameters.
On Wed, Apr 8, 2015 at 9:34 AM, Adrian Klaver
wrote:
> On 04/08/2015 07:22 AM, Andrew Pennebak
":db"
Is there a flag I can give to ecpg to ignore input parameters?
Is there a patch we could make to ecpg to accept input parameters?
Is there another way to write my input parameters to work around this error?
--
Cheers,
Andrew Pennebaker
www.yellosoft.us
On April 2, 2015, Scott Ribe wrote:
> On Apr 2, 2015, at 10:14 PM, Adrian Klaver wrote:
> > EXECUTE 'insert into ' || quote_ident(tblname) || ' values(' || new.* ||
> > ')'
>
> Not that easy, strings are not quoted correctly, and null values are blank.
> Might be a function to translate new.* into
ring and are
> consuming by far the most disk space (still somewhat expensive on SSD)!
This doesn't actually solve your problem, but you could mitigate the
cost by putting those tables on spinning-rust disks using tablespaces
or symlinks or whatever.
Best regards,
A
--
Andrew Sullivan
corruption fixes since 9.0.4. You should always try to
stay on the latest minor release of your version of Postgres.
Best regards,
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.p
ure it does the thing requested in this case.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
don't know
whether Bucardo or Londiste (two alternative systems that work on
roughly the same principle) have this functionality, but I kind of
doubt it since both were designed to get rid of several of the
complexities that Slony presented. (Slony had all those complexities
because it w
we'll output it. But we're not going to silently convert infinity to
anything else:
andrew=# select to_json('9-12-31'::timestamptz);
to_json
--
"9-12-31T00:00:00-05:00"
cheers
andrew
--
Sent via pgsql-
use-cases.
So +1 for removing the error and emitting "infinity" suitably quoted.
Andrew, will you do that?
Yeah.
cheers
andrew
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresq
onstraints" - breathe slowly in, and out, in,
and out.
It looks to me like ab14a73a6ca5cc4750f0e00a48bdc25a2293034a copied too
much code from xml.c - including a comment about XSD... Andrew, was that
intentional?
Not wanting to put words in Andrew's mouth, but I thought the point of
those changes
eathe slowly in, and out, in,
and out.
It looks to me like ab14a73a6ca5cc4750f0e00a48bdc25a2293034a copied too
much code from xml.c - including a comment about XSD... Andrew, was that
intentional?
Possibly too much was copied, I don't recall a reason offhand for
excluding infinity. I'
s dramatically reduced the number of such
cases. Some convenience was lost (I still get tripped up from time to
time, but I'm not doing Pg work every day), but the overall
reliability of things was increased. So I'd say it's probably not a
bug.
A
--
Andrew Sullivan
a...@crankyc
SAVEPOINT foo;
Q2;
if error then
ROLLBACK;
These both work. The problem is, I think, that you have different
rules for "when Q2 fails", and without knowing your exact
circumstances I suspect we can't say much more. Indeed, however, it
sounds to me like you think these are in the same wor
bering this thread. So there's a field report :-)
+0.75 for backpatching (It's hard to imagine someone relying on the bad
behaviour, but you never know).
cheers
andrew
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
that many people are using for
IDNA2008:
<https://gitorious.org/libidn2/libidn2/source/0d6b5c0a9f1e4a9742c5ce32b6241afb4910cae1:>
It's GPLv3, though, which brings its own issues.
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (pgsql-general@
1 - 100 of 1437 matches
Mail list logo
