* Do we need some kind of assistance from a foundation or establish a
>> foundation?
>> There should be many, many software to address, so the ecosystem
>> activity has to be long-lasting. Plus, money and expertise is necessary.
>> Would we benefit if we join the Linux Foundatio
from source you can go there to build the module.
cnpusr
2015-01-15
--
Adrian Klaver
adrian.kla...@aklaver.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 12/29/2014 09:55 AM, Tom Lane wrote:
Adrian Klaver writes:
So it seems you can turn ON_ERROR_ROLLBACK on with either 1 or 'on', but you
can only turn it off with 'off'.
With ON_ERROR_STOP 1/on and 0/off both seem to work.
Is this expected?
Given the lack of
as the server?
issue: psql client generates a core when up arrow is used twice.
Regards
Tarkeshwar
--
Adrian Klaver
adrian.kla...@aklaver.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
LECT EXISTS (SELECT * FROM list WHERE file = '') AND
NOT EXISTS (SELECT * FROM list WHERE file = '0001') AND
NOT EXISTS (SELECT * FROM list WHERE file = '') AND
EXISTS (SELECT * FROM list WHERE file != '')
AS file_000
On 05/30/2014 01:31 PM, Tom Lane wrote:
Adrian Klaver writes:
On 05/30/2014 11:52 AM, Tom Lane wrote:
If you do the ld call by hand without the -syslibroot option, it works.
AFAICS it could never have worked with such an option, so I'm thinking
this is some new misbehavior in the l
that goes into detail on this is here:
http://stackoverflow.com/questions/19555395/python-framework-is-missing-from-os-x-10-9-sdk-why-also-workaround
The Apple document referenced in above is:
https://developer.apple.com/library/ios/technotes/tn2328/_index.html
regards
On 02/25/2014 10:54 AM, Josh Berkus wrote:
On 02/25/2014 10:50 AM, Robert Haas wrote:
On Tue, Feb 25, 2014 at 1:45 PM, Josh Berkus wrote:
On 02/25/2014 10:31 AM, Robert Haas wrote:
And I definitely don't
agree that our documentation should push people towards stuffing
everything in a JSON blo
|
open | timestamp without time zone |
Triggers:
test_open AFTER INSERT ON test_open FOR EACH ROW EXECUTE PROCEDURE
test_open()
test=> INSERT INTO test_open (id,open) VALUES (1,now());
INSERT 0 1
Thanks in advance.
regards,
--
Adrian Klaver
adrian.kla...@gmail.com
ndows world there is a fairly sharp
demarcation between users and developers. So use does not necessarily
mean developer knowledge.
regards, tom lane
--
Adrian Klaver
adrian.kla...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
T
PST-0LOG: parameter "max_connections" cannot
be changed without restarting the server
-2014-01-21 14:42:23.169 PST-0LOG: configuration file
"/usr/local/pgsql93/data/postgresql.conf" contains errors; unaffected
changes were applied
--
Adrian Klaver
adrian.kla...@gmail
u wanted a change in a value, the change did not occur, hence an error.
I've tested this on 9.3 and 9.4devel.
Thom
--
Adrian Klaver
adrian.kla...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 01/12/2014 08:04 PM, Bruce Momjian wrote:
On Sun, Jan 12, 2014 at 07:58:52PM -0800, Adrian Klaver wrote:
Well the problem is that it actually points to a current PGDATA just
the wrong one. To use the source installation path and the suggested
upgrade method from pg_upgrade.
In the
On 01/12/2014 07:02 PM, Bruce Momjian wrote:
On Sun, Jan 12, 2014 at 12:48:40PM -0500, Tom Lane wrote:
Bruce Momjian writes:
On Sat, Jan 11, 2014 at 12:48:51PM -0800, Adrian Klaver wrote:
I see, though I have another question. If pg_tablespace and the
symlinks can get out of sync, as you say
On 01/11/2014 10:55 AM, Bruce Momjian wrote:
On Sat, Jan 11, 2014 at 10:40:20AM -0800, Adrian Klaver wrote:
Right. I know there were multiple issue with this upgrade, jails
probably being the biggest, but a new one I had never heard is that _if_
you are placing your tablespaces in the PGDATA
On 01/10/2014 04:48 PM, Joshua D. Drake wrote:
On 01/10/2014 04:38 PM, Stephen Frost wrote:
Adrian,
* Adrian Klaver (adrian.kla...@gmail.com) wrote:
On 01/10/2014 04:25 PM, Stephen Frost wrote:
* Adrian Klaver (adrian.kla...@gmail.com) wrote:
A) Change the existing sync mode to allow the
On 01/10/2014 04:25 PM, Stephen Frost wrote:
Adrian,
* Adrian Klaver (adrian.kla...@gmail.com) wrote:
A) Change the existing sync mode to allow the master and standby
fall out of sync should a standby fall over.
I'm not sure that anyone is argueing for this..
Looks like here, unless
Then it is up to the documentation to
clearly point out the benefits/pitfalls. If you want to implement
something as important as replication without reading the docs then the
results are on you.
JD
--
Adrian Klaver
adrian.kla...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hacker
inues.
Why is that configuration advantageous over a async configuration is the
question. Why, with those requirements, are you using a synchronous
standby at all?
+1
Greetings,
Andres Freund
--
Adrian Klaver
adrian.kla...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-ha
ght I suggest a cooling off period and
a return to the discussion in possibly a Wiki page where the
points/counter points could be laid out more efficiently?
Andres
--
Adrian Klaver
adrian.kla...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
and out, start
with reasonable expectation of protection. This is a GUC so it can be
modified to suite personal taste.
--
Adrian Klaver
adrian.kla...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
a reply, so that email
> clients can do a reasonable job sorting the two threads together. Yes,
> email is stupid.
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hack
emicolon-after-begin-is-not-allowed-in-postgresql-tp5779905.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
--
Adrian Klaver
adrian.kla...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.
On 11/16/2013 03:46 PM, Marko Kreen wrote:
On Sat, Nov 16, 2013 at 03:21:19PM -0800, Adrian Klaver wrote:
On 11/16/2013 03:09 PM, Marko Kreen wrote:
On Sat, Nov 16, 2013 at 02:54:22PM -0800, Adrian Klaver wrote:
On 11/16/2013 02:41 PM, Marko Kreen wrote:
If you don't see any other i
On 11/16/2013 03:09 PM, Marko Kreen wrote:
On Sat, Nov 16, 2013 at 02:54:22PM -0800, Adrian Klaver wrote:
On 11/16/2013 02:41 PM, Marko Kreen wrote:
If you don't see any other issues perhaps they are ready for committer?
I do not have any other questions/issues at this point. I am new t
On 11/16/2013 02:41 PM, Marko Kreen wrote:
On Sat, Nov 16, 2013 at 02:07:57PM -0800, Adrian Klaver wrote:
On 11/16/2013 01:13 PM, Marko Kreen wrote:
https://commitfest.postgresql.org/action/patch_view?id=1310
Got it, applied it.
Results:
openssl ciphers -v 'HIGH:!aNULL'|e
On 11/16/2013 01:13 PM, Marko Kreen wrote:
On Sat, Nov 16, 2013 at 01:03:05PM -0800, Adrian Klaver wrote:
On 11/16/2013 12:37 PM, Marko Kreen wrote:
Thanks for testing!
On Sat, Nov 16, 2013 at 12:17:40PM -0800, Adrian Klaver wrote:
On 11/16/2013 06:24 AM, Marko Kreen wrote:
ssl-better
On 11/16/2013 12:37 PM, Marko Kreen wrote:
Thanks for testing!
On Sat, Nov 16, 2013 at 12:17:40PM -0800, Adrian Klaver wrote:
On 11/16/2013 06:24 AM, Marko Kreen wrote:
ssl-better-default:
SSL should stay working, openssl ciphers -v 'value' should not contain
any weak suites
On 11/16/2013 06:24 AM, Marko Kreen wrote:
On Fri, Nov 15, 2013 at 02:16:52PM -0800, Adrian Klaver wrote:
On 11/15/2013 11:49 AM, Marko Kreen wrote:
On Fri, Nov 15, 2013 at 11:16:25AM -0800, Adrian Klaver wrote:
The description of the GUCs show up in the documentation but I am
not seeing the
On 11/15/2013 11:49 AM, Marko Kreen wrote:
On Fri, Nov 15, 2013 at 11:16:25AM -0800, Adrian Klaver wrote:
The description of the GUCs show up in the documentation but I am
not seeing the GUCs themselves in postgresql.conf, so I could test
no further. It is entirely possible I am missing a step
possible I am missing a step and would
appreciate enlightenment.
The general premise seems sound, allowing the DBA control over the type
of cipher of used.
Thanks,
--
Adrian Klaver
adrian.kla...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to
=postgresql.git;a=commit;h=7778ddc7a2d5b006edbfa69cdb44b8d8c24ec1ff
Is a review necessary at this point?
--
Adrian Klaver
adrian.kla...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
s database
that also fine to me.
I wanted to connect patnaonlinedb any how and wanted to perform backup
of this , Solution please.
--
Adrian Klaver
adrian.kla...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Also it not necessary to use FULL with the VACUUM.
Thanks in advance.
Shailesh Singh
--
Adrian Klaver
adrian.kla...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
art of the
core code. Not sure if it is the projects responsibility to maintain
transparency with the feature matrices of external projects.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Adrian Klaver
adrian.kla...@gmail.com
--
Sent via pgsql-hackers
On 03/23/2013 08:16 AM, Tom Lane wrote:
Adrian Klaver writes:
Seems the time zone info still thinks Moscow time is being setting
forward an hour for DST when in fact the time remains constant through
the year.
I think the discrepancy is between this in timezone/data/europe:
Zone Europe
On 02/08/2013 10:09 AM, Tom Lane wrote:
Adrian Klaver writes:
I am not sure I am following. Are we talking two different cases here?
What I was pointing out was that the non-superuser case seems to be
broken almost completely, whereas the superuser case is only broken
if the object owner has
On 02/08/2013 09:09 AM, Tom Lane wrote:
Adrian Klaver writes:
On 02/08/2013 08:14 AM, Tom Lane wrote:
Of course, postgres has other options besides that, of which "DROP OWNED
BY ak02" is probably the most appropriate here. Or if you really want
to get rid of just that grant, S
ns are for the
extension mechanism. There is also the issue of backward compatibility
for those people that are using configuration tables in their extensions
and would like to maintain that separation. I could see adding another
function that is similar and would be used to identify strictly
>
> This is trivial to fix, now that we know there's a problem --- the
> function is only using that assumption to save itself a couple lines
> of code. Penny wise, pound foolish :-(
I killed a few brain cells just reading the explanation:)
>
> regards,
On 03/31/2011 08:27 AM, Brendan Jurd wrote:
On 1 April 2011 02:00, Adrian Klaver wrote:
On Wednesday, March 30, 2011 8:39:25 pm Brendan Jurd wrote:
If we wanted to make it "work", then I think the thing to do would be
to add a new set of formatting tokens IDY, IDAY etc. I don'
On Wednesday, March 30, 2011 8:39:25 pm Brendan Jurd wrote:
> On 31 March 2011 03:15, Steve Crawford wrote:
> > On 03/29/2011 04:24 PM, Adrian Klaver wrote:
> >> ...
> >> Well the strange part is only fails for SUN:...
> >> test(5432)aklaver=>se
On 03/30/2011 09:15 AM, Steve Crawford wrote:
On 03/29/2011 04:24 PM, Adrian Klaver wrote:
...
Well the strange part is only fails for SUN:...
test(5432)aklaver=>select to_date('2011-13-SUN', 'IYYY-IW-DY');
to_date
2011-03-28
...
You specified Sunday
://en.wikipedia.org/wiki/Quantum_computer). The intersection of
NoSQL and Quantum decoherence is almost to good to be true.
--
Adrian Klaver
adrian.kla...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
44 matches
Mail list logo
