2016-11-29 17:12 GMT+01:00 Stephen Frost :
> Guillaume, Amul,
>
> * Amul Sul (sula...@gmail.com) wrote:
> > The following review has been posted through the commitfest application:
> > make installcheck-world: tested, passed
> > Implements feature: tested, passed
> > Spec compliant:
Hi,
While translating the 9.5 ref/psql-ref.sgml, I found this:
and variables shows help about about
psql configuration variables
The word "about" is written twice. Sounds like a nice typo to me :)
See attached patch (for 9.5 and HEAD).
Thanks.
--
Guillaume.
http://blog.guillaume.lelarge.i
Le 24 nov. 2015 01:05, "Michael Paquier" a
écrit :
>
> On Tue, Nov 24, 2015 at 3:41 AM, Kevin Grittner wrote:
> > Yahoo recently changed their DMARC policy, and after some
> > investigation and a support case with Yahoo, it is now clear that
> > their email systems can no longer be used with the
Le 22 nov. 2015 21:29, "Pavel Stehule" a écrit :
>
>
>
> 2015-11-22 21:19 GMT+01:00 Jim Nasby :
>>
>> On 11/22/15 2:11 PM, Pavel Stehule wrote:
>>>
>>> What about pg_size(text), pg_size(value bigint, unit text) ?
>>
>>
>> I like, though I'd make it numeric or float. pg_size(3.5, 'GB')
certainly se
Hi,
Le 12 nov. 2015 1:05 AM, "Michael Paquier" a
écrit :
>
> On Thu, Nov 12, 2015 at 12:41 AM, Nikolay Shaplov
> wrote:
> > В письме от 28 октября 2015 16:57:36 пользователь Michael Paquier
написал:
> >> On Sat, Oct 17, 2015 at 1:48 AM, Michael Paquier wrote:
> >> > On Sat, Oct 17, 2015 at 5:15
2015-08-20 18:43 GMT+02:00 Kevin Burke :
> Hi,
> Normally I try to annotate incoming queries, to make it easier to diagnose
> slow ones. For example:
>
> -- Users.findByPhoneNumber
> SELECT * FROM
>
> The pg_dump and pg_restore commands issue a COPY with no possibility of
> adding a comment.
Le 6 juil. 2015 7:16 PM, "Данила Поярков" a écrit :
>
> Hello!
>
> What is the best starting point to PostgreSQL internal APIs for operating
directly with the storage (performing basic INSERTs, UPDATEs, SELECTs and
simple JOINs by hand)? I'm looking for something similar to MySQL Cluster
NDB API o
Le 2 juil. 2015 7:28 AM, "Simon Riggs" a écrit :
>
> On 2 July 2015 at 03:00, Rahila Syed wrote:
>
>>
>> >Yes, I suggest just a single column on pg_stat_activity called
pct_complete
>>
>> Reporting remaining time also can be crucial to make decisions regarding
continuing or aborting VACUUM.
>> Th
2015-01-05 17:44 GMT+01:00 Guillaume Lelarge :
> 2015-01-05 17:40 GMT+01:00 Robert Haas :
>
>> On Wed, Dec 31, 2014 at 12:46 PM, Tom Lane wrote:
>> > I'd be all right with putting the data structure declarations in a file
>> > named something like autovacuum_
Le 2 juin 2015 6:37 AM, "Michael Nolan" a écrit :
>
> Why not take a simpler approach and create a zero length file in
directories that should not be fiddled with by non-experts using a file
name something like "DO.NOT.DELETE.THESE.FILES"?
>
> No, it won't prevent the incredibly stupid from doing
Le 29 mai 2015 8:01 AM, "Fabien COELHO" a écrit :
>
>
>> FWIW, I don't mind which one we put in core and which one we put out of
>> core. But I like Joshua's idea of getting rid of contribs and pushing
them
>> out as any other extensions.
>
>
> Hmmm.
>
> I like the contrib directory as a living ex
Le 29 mai 2015 8:10 AM, "Pavel Stehule" a écrit :
>
> Hi
>
> I am not sure if PGXN can substitute contrib - mainly due deployment - It
doesn't helps with MS Windows. Installing necessary software for
compilation there is terrible.
>
I agree it's hard to compile an extension on Windows, but that's
Le 29 mai 2015 5:33 AM, "Joshua D. Drake" a écrit :
>
>
> On 05/28/2015 08:10 PM, Stephen Frost wrote:
>>
>> JD,
>
>
This seems reasonable to me. It's in line with the recent move from
contrib to bin. It'll just be quite a bit bigger of an undertaking.
(50 threads to discuss the m
2015-05-27 0:01 GMT+02:00 Martín Marqués :
> El 25/05/15 a las 06:13, alex2010 escribió:
> > Maybe it makes sense to add ability to store large objects in the same
> table space as the table.
> > Or an opportunity - to specify table space for a large object.
> > Do you have anything in todolists
2015-02-04 6:37 GMT+01:00 Tom Lane :
> Stephen Frost writes:
> > All,
> > We recently had a client complain that check_postgres' commitratio
> > check would alert about relatively unused databases. As it turns
> > out, the reason for this is because they automate running pg_dump
> > agai
2015-01-05 17:40 GMT+01:00 Robert Haas :
> On Wed, Dec 31, 2014 at 12:46 PM, Tom Lane wrote:
> > I'd be all right with putting the data structure declarations in a file
> > named something like autovacuum_private.h, especially if it carried an
> > annotation that "if you depend on this, don't be
2014-12-30 18:45 GMT+01:00 Jeff Janes :
> On Tue, Dec 30, 2014 at 12:35 AM, Guillaume Lelarge <
> guilla...@lelarge.info> wrote:
>
>> Sorry for my very late answer. It's been a tough month.
>>
>> 2014-11-27 0:00 GMT+01:00 Bruce Momjian :
>>
>>>
2014-12-12 14:58 GMT+01:00 Heikki Linnakangas :
> On 12/10/2014 04:32 PM, Dennis Kögel wrote:
>
>> Hi,
>>
>> Am 04.09.2014 um 17:50 schrieb Jehan-Guillaume de Rorthais <
>> j...@dalibo.com>:
>>
>>> Since few months, we occasionally see .ready files appearing on some
>>> slave
>>> instances from va
Sorry for my very late answer. It's been a tough month.
2014-11-27 0:00 GMT+01:00 Bruce Momjian :
> On Mon, Nov 3, 2014 at 12:39:26PM -0800, Jeff Janes wrote:
> > It looked to me that the formula, when descending from a previously
> stressed
> > state, would be:
> >
> > greatest(1 + checkpoint_c
2014-12-29 17:03 GMT+01:00 Tom Lane :
> Guillaume Lelarge writes:
> > All in all, I want to get informations that are typically stored in
> shared
> > memory, handled by the autovacuum launcher and autovacuum workers. I
> first
> > thought I could get that by writing s
Hey,
There are times where I would need more informations on the autovacuum
processes.
I'd love to know what each worker is currently doing. I can get something
like this from the pg_stat_activity view but it doesn't give me as much
informations as the WorkerInfoData struct.
I'd also love to hav
2014-12-07 15:07 GMT+01:00 Heikki Linnakangas :
> On 12/07/2014 02:03 PM, Guillaume Lelarge wrote:
>
>> Hi,
>>
>> I've been reading the FSM README file lately
>> (src/backend/storage/freespace/README), and I'm puzzled by one of the
>> graph
>>
Hi,
I've been reading the FSM README file lately
(src/backend/storage/freespace/README), and I'm puzzled by one of the graph
(the binary tree structure of an FSM file). Here it is:
4
4 2
3 4 0 2<- This level represents heap pages
Shouldn't the last line be:
4 3 2 0
(ie, highest
Hi,
Le 15 oct. 2014 22:25, "Guillaume Lelarge" a écrit
:
>
> 2014-10-15 22:11 GMT+02:00 Jeff Janes :
>>
>> On Fri, Aug 8, 2014 at 12:08 AM, Guillaume Lelarge <
guilla...@lelarge.info> wrote:
>>>
>>> Hi,
>>>
>>> As part of our
2014-10-15 23:12 GMT+02:00 Josh Berkus :
> On 10/15/2014 01:25 PM, Guillaume Lelarge wrote:
> > Monitoring is another matter, and I don't really think a monitoring
> > solution should count the WAL files. What actually really matters is the
> > database availability
2014-10-15 22:11 GMT+02:00 Jeff Janes :
> On Fri, Aug 8, 2014 at 12:08 AM, Guillaume Lelarge > wrote:
>
>> Hi,
>>
>> As part of our monitoring work for our customers, we stumbled upon an
>> issue with our customers' servers who have a wal_keep_segments set
Le 8 août 2014 09:08, "Guillaume Lelarge" a écrit :
>
> Hi,
>
> As part of our monitoring work for our customers, we stumbled upon an
issue with our customers' servers who have a wal_keep_segments setting
higher than 0.
>
> We have a monitoring script that chec
Hi,
Le 9 août 2014 05:57, "Ramirez, Danilo" a écrit :
>
> Thanks to all for the great info. We are new to postgresql and this
discussion has both instructed us and increased our respect for the
database and the community.
>
> I am seeing a behavior that I don’t understand and hopefully you guys
Hi,
As part of our monitoring work for our customers, we stumbled upon an issue
with our customers' servers who have a wal_keep_segments setting higher
than 0.
We have a monitoring script that checks the number of WAL files in the
pg_xlog directory, according to the setting of three parameters
(c
Hi,
Still translating the 9.4 manual, and found another typo. Patch attached.
Thanks.
--
Guillaume.
http://blog.guillaume.lelarge.info
http://www.dalibo.com
diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index d3fcb82..cf174f0 100644
--- a/doc/src/sgml/maintenan
Hi,
While updating the french translation of the latest releases, I stumbled
upon a small issue on the config.sgml file.
It talks about unix_socket_directories whereas this parameter only appears
with the 9.3 release. It should probably be replaced with
unix_socket_directory for all releases wher
Le 9 juil. 2014 20:36, "David G Johnston" a
écrit :
>
> csrajmohan wrote
> > "EXPLAIN (format XML) " command in PostgreSQL9.3.4 gives the plan chosen
> > by
> > the optimizer in XML format. In my program, I have to extract certain
data
> > about optimizer plan from this XML output. I am using *Lib
On Fri, 2014-05-09 at 17:16 -0400, Stephen Frost wrote:
> Guillaume,
>
> * Guillaume Lelarge (guilla...@lelarge.info) wrote:
> > Should information_schema tables be moved and not pg_catalog ones? it
> > doesn't seem consistent to me.
>
> The catalog tables are
Hey,
I was working on adding support to the new MOVE clause of the ALTER
TABLESPACE statement to pgAdmin when I noticed this issue. See this
example:
Fresh git compilation, and new database on a new cluster:
$ createdb b1
$ psql b1
psql (9.4devel)
Type "help" for help.
b1=# CREATE TABLESPACE ts
On Sat, 2014-03-22 at 11:23 -0500, Jim Nasby wrote:
> On 3/21/14, 8:13 PM, David E. Wheeler wrote:
> > On Mar 21, 2014, at 2:16 PM, Andrew Dunstan wrote:
> >
> >> Surely if it were really a major annoyance, someone would have sent code
> >> to fix it during the last 4 years and more since the abo
On Wed, 2013-03-20 at 13:13 -0300, Alvaro Herrera wrote:
> Marc Cousin escribió:
> > On 20/03/2013 16:33, Alvaro Herrera wrote:
>
> > >Ah. The reason for this problem is that the statement start time (which
> > >also sets the transaction start time, when it's the first statement) is
> > >set by p
On Sun, 2013-03-17 at 14:13 -0400, Tom Lane wrote:
> Guillaume Lelarge writes:
> > On Sun, 2013-03-17 at 16:06 +, Tom Lane wrote:
> >> Move pqsignal() to libpgport.
>
> > When I try to compile HEAD right after this commit, I have this issue
> > with pg_rece
On Sun, 2013-03-17 at 16:06 +, Tom Lane wrote:
> Move pqsignal() to libpgport.
>
> We had two copies of this function in the backend and libpq, which was
> already pretty bogus, but it turns out that we need it in some other
> programs that don't use libpq (such as pg_test_fsync). So put it w
On Mon, 2012-12-31 at 17:44 -0300, Alvaro Herrera wrote:
> Alvaro Herrera wrote:
> > Guillaume Lelarge wrote:
> > > On Mon, 2012-12-31 at 11:03 -0300, Alvaro Herrera wrote:
> >
> > > > I think this (have a config option, and have SIGHUP work as expected
On Mon, 2012-12-31 at 12:54 -0300, Alvaro Herrera wrote:
> Guillaume Lelarge wrote:
> > On Mon, 2012-12-31 at 11:03 -0300, Alvaro Herrera wrote:
>
> > > I think this (have a config option, and have SIGHUP work as expected)
> > > would be useful to demo in worker_spi,
On Mon, 2012-12-31 at 11:03 -0300, Alvaro Herrera wrote:
> Guillaume Lelarge wrote:
> > Hi,
> >
> > Today, I tried to make fun with the new background worker processes in
> > 9.3, but I found something disturbing, and need help to go further.
>
> Thanks.
>
Hi,
Today, I tried to make fun with the new background worker processes in
9.3, but I found something disturbing, and need help to go further.
My code is available on https://github.com/gleu/stats_recorder. If you
take a look, it is basically a copy of Alvarro's worker_spi contrib
module with a f
On Sat, 2012-10-20 at 14:28 -0400, Tom Lane wrote:
> I wrote:
> > It looks like I broke this in commit
> > 4317e0246c645f60c39e6572644cff1cb03b4c65, because I removed this from
> > _tocEntryRequired():
>
> > - /* Ignore DATABASE entry unless we should create it */
> > - if (!ropt->createDB &&
On Thu, 2012-10-18 at 12:19 -0300, Alvaro Herrera wrote:
> Robert Haas escribió:
> > On Tue, Oct 16, 2012 at 10:31 AM, Guillaume Lelarge
> > wrote:
> > > Any comments on this?
> >
> > I'm not sure I'd want to back-patch this, since it is a behavior
&
On Sat, 2012-10-13 at 16:47 +0200, Guillaume Lelarge wrote:
> Hi,
>
> One of my colleagues, Jehan-Guillaume de Rorthais, found a weird
> behaviour of the "-c" command line option in the pg_restore tool while
> doing a training. Here is the following steps he fo
Hi,
One of my colleagues, Jehan-Guillaume de Rorthais, found a weird
behaviour of the "-c" command line option in the pg_restore tool while
doing a training. Here is the following steps he followed:
createdb foo
pg_dump -Fc foo > foo.dump
createdb bar
pg_restore -c -d bar foo.dump
bar contains
Hi Pavel,
On Mon, 2012-06-25 at 08:26 +0300, Pavel Golub wrote:
> Hello, Pgsql-bugs.
>
> According to the "Moving tablespaces" thread started by Bruce
> http://archives.postgresql.org/pgsql-docs/2011-12/msg3.php
> pg_tablespace.spclocation column is removed in the 9.2beta. However
> this brea
On Sat, 2012-04-21 at 07:03 +0530, Amit Kapila wrote:
> If I understood correctly the following query should give your answer:
> Select opcintype from pg_opclass where opcname = '';
You're right, and my question was wrong. I finally found the SQL query I
was looking for.
Thanks.
--
Guillaume
h
Hi,
I'm working on adding support of range types in pgAdmin and I have a
really hard time understanding the subtype parameter of a range type.
How can I find all the types associated with a specific operator class?
I'm pretty sure it's a really dumb question, but I'm completely lost
here.
Thanks.
On Mon, 2012-04-16 at 13:09 +0300, Heikki Linnakangas wrote:
> On 13.04.2012 19:17, Guillaume Lelarge wrote:
> > On Thu, 2012-04-12 at 12:28 +0300, Heikki Linnakangas wrote:
> >> On 08.04.2012 11:59, Guillaume Lelarge wrote:
> >>> There could be a good reason which
On 04/13/2012 08:15 PM, Kevin Grittner wrote:
Robert Haas wrote:
In my view, remote_write seems a lot more clear than write
+1
I sure didn't understand it to mean remote_write when I read the
subject line.
Neither did I. So definitely +1.
--
Guillaume
http://www.postgresql.fr
http://
On Thu, 2012-04-12 at 12:28 +0300, Heikki Linnakangas wrote:
> On 08.04.2012 11:59, Guillaume Lelarge wrote:
> > Hi,
> >
> > I recently wrote a plpgsql plugin. I wanted to enable the use of pgxs,
> > to make it easier to compile the plugin, but I eventually found that
Hi,
I recently wrote a plpgsql plugin. I wanted to enable the use of pgxs,
to make it easier to compile the plugin, but I eventually found that I
can't do that because the plpgsql.h file is not available in the include
directory.
I'm wondering if we shouldn't put the header files of plpgsql sourc
On Thu, 2012-02-16 at 19:27 -0500, Tom Lane wrote:
> Guillaume Lelarge writes:
> > This query:
> > SELECT ARRAY[-1,3,1] & ARRAY[1, 2];
> > should give {1} as a result.
>
> > But, on HEAD (and according to his tests, on 9.0.6 and 9.1.2), it
> > appears t
Hi,
On a french PostgreSQL web forum, one of our users asked about a curious
behaviour of the intarray extension.
This query:
SELECT ARRAY[-1,3,1] & ARRAY[1, 2];
should give {1} as a result.
But, on HEAD (and according to his tests, on 9.0.6 and 9.1.2), it
appears to give en empty array.
Digg
On Mon, 2011-12-26 at 16:23 +0100, Magnus Hagander wrote:
> On Mon, Dec 26, 2011 at 15:59, Alexander Björnhagen
> wrote:
> Basically I like this whole idea, but I'd like to know why do you think
> this functionality is required?
> >
> >>> How should a synchronous master handle the situa
Le 26/03/2011 02:43, Tomas Vondra a écrit :
> Dne 26.3.2011 02:05, Joshua Berkus napsal(a):
>> Tomas,
>>
>>> I spoke to a teacher from a local university last week, mainly as we
>>> were looking for a place where a local PUG could meet regularly. I
>>> realized this could be a good opportunity to h
Le 23/03/2011 17:53, Tom Lane a écrit :
> Robert Haas writes:
>> On Tue, Mar 22, 2011 at 6:23 PM, Guillaume Lelarge
>> wrote:
>>> While working on adding support for SQL/Med objects to pgAdmin, I'm
>>> quite surprised to see there is no way to add comme
Hi,
While working on adding support for SQL/Med objects to pgAdmin, I'm
quite surprised to see there is no way to add comments to SQL/Med
objects. Is this on purpose or is it just something that was simply missed?
Thanks.
--
Guillaume
http://www.postgresql.fr
http://dalibo.com
--
Sent via
Le 01/01/2011 16:00, Robert Haas a écrit :
> On Sat, Jan 1, 2011 at 9:53 AM, Guillaume Lelarge
> wrote:
>> Le 01/01/2011 06:05, Robert Haas a écrit :
>>> On Fri, Dec 31, 2010 at 8:48 AM, Peter Eisentraut wrote:
>>>> On tor, 2010-12-30 at 11:03 -0500, Rober
Le 01/01/2011 06:05, Robert Haas a écrit :
> On Fri, Dec 31, 2010 at 8:48 AM, Peter Eisentraut wrote:
>> On tor, 2010-12-30 at 11:03 -0500, Robert Haas wrote:
>>> No, quite the opposite. With the other approach, you needed:
>>>
>>> constraints cannot be used on views
>>> constraints cannot be use
Le 28/12/2010 19:30, Tom Lane a écrit :
> Gurjeet Singh writes:
>> On Tue, Dec 28, 2010 at 12:12 PM, Robert Haas wrote:
>>> SQL access is frequently more convenient, though. Although maybe now that
>>> we've made recovery.conf use the GUC lexer we oughta continue in that vein
>>> and expose thos
Le 28/12/2010 18:12, Robert Haas a écrit :
> On Dec 28, 2010, at 10:34 AM, Tom Lane wrote:
>> I'm still wondering what's the actual use-case for exposing this inside
>> SQL. Those with a legitimate need-to-know can look at the slave
>> server's config files, no?
>
> SQL access is frequently more
Le 28/12/2010 17:50, Gurjeet Singh a écrit :
> On Tue, Dec 28, 2010 at 11:36 AM, Tom Lane wrote:
>
>>
>> I can see the point of, say, a primary_host_address() function returning
>> inet, which would be way better on both those dimensions than the
>> current proposal. But I'm not sure what else w
Le 28/12/2010 17:36, Tom Lane a écrit :
> Guillaume Lelarge writes:
>> Le 28/12/2010 16:34, Tom Lane a écrit :
>>> I'm still wondering what's the actual use-case for exposing this inside
>>> SQL. Those with a legitimate need-to-know can look at the slave
>
Le 28/12/2010 16:34, Tom Lane a écrit :
> Magnus Hagander writes:
>> On Dec 28, 2010 3:58 PM, "Tom Lane" wrote:
>>> What's the use case? And aren't there security reasons to NOT expose
>>> that? It might contain a password for instance.
>
>> Good point - should be made superuser only.
>
> I'm
Le 27/09/2010 15:18, Robert Haas a écrit :
> 2010/9/27 Devrim GÜNDÜZ :
>> Attached is a small patch that adds a few comments for the settings that
>> require restart. Applicable for 9.0+.
>
> I'm not sure this is worth back-patching, but I've committed it to the
> master branch.
>
+1 for backpat
Le 21/07/2010 09:53, Dave Page a écrit :
> On Tue, Jul 20, 2010 at 8:12 PM, Peter Eisentraut wrote:
>>> My preference would be to stick to a style where we identify the
>>> committer using the author tag and note the patch author, reviewers,
>>> whether the committer made changes, etc. in the comm
Le 21/07/2010 23:23, Andreas Joseph Krogh a écrit :
> [...]
> I was googling for how to create a text-seach-config with the following
> properties:
> - Map unicode accentuated letters to an un-accentuated equivalent
> - No stop-words
> - Lowercase all words
>
> And came over this from -general:
>
Le 15/07/2010 17:48, Joshua D. Drake a écrit :
> On Thu, 2010-07-15 at 16:20 +0100, Simon Riggs wrote:
>> On Thu, 2010-07-15 at 11:05 -0400, Tom Lane wrote:
>>> Simon Riggs writes:
The biggest turn off that most people experience when using PostgreSQL
is that psql does not support memora
Le 01/07/2010 22:13, Robert Haas a écrit :
> On Thu, Jul 1, 2010 at 12:11 PM, Guillaume Lelarge
> wrote:
>> Le 01/07/2010 17:54, Robert Haas a écrit :
>>> On Thu, Jul 1, 2010 at 10:18 AM, Robert Haas wrote:
>>>> On Thu, Jul 1, 2010 at 5:30 AM, Guillaume Lelarge
Le 01/07/2010 17:54, Robert Haas a écrit :
> On Thu, Jul 1, 2010 at 10:18 AM, Robert Haas wrote:
>> On Thu, Jul 1, 2010 at 5:30 AM, Guillaume Lelarge
>> wrote:
>>>>>> On Tue, Jun 29, 2010 at 9:42 PM, Bruce Momjian wrote:
>>>>>>> So this i
Le 30/06/2010 06:53, Guillaume Lelarge a écrit :
> Le 30/06/2010 05:25, Tom Lane a écrit :
>> Robert Haas writes:
>>> On Tue, Jun 29, 2010 at 9:42 PM, Bruce Momjian wrote:
>>>> So this is not something we want fixed for 9.0, as indicated by Simon?
>>>>
Le 30/06/2010 05:25, Tom Lane a écrit :
> Robert Haas writes:
>> On Tue, Jun 29, 2010 at 9:42 PM, Bruce Momjian wrote:
>>> So this is not something we want fixed for 9.0, as indicated by Simon?
>>> I don't see the patch on the commit-fest page yet.
>
>> I tend to think we should fix it for 9.0,
Le 23/06/2010 23:29, Guillaume Lelarge a écrit :
> Le 23/06/2010 22:54, Tom Lane a écrit :
>> Robert Haas writes:
>>> On Mon, Jun 21, 2010 at 12:46 PM, Guillaume Lelarge
>>> wrote:
>>>> I added a CHECK_FOR_INTERRUPTS call in the copy_relation_data(),
>
Le 23/06/2010 22:54, Tom Lane a écrit :
> Robert Haas writes:
>> On Mon, Jun 21, 2010 at 12:46 PM, Guillaume Lelarge
>> wrote:
>>> I added a CHECK_FOR_INTERRUPTS call in the copy_relation_data(),
>>> copy_dir(), and copy_file() functions. Works for me on ALTER
Le 22/06/2010 11:41, Simon Riggs a écrit :
> On Tue, 2010-06-22 at 09:54 +0200, Guillaume Lelarge wrote:
>> I added support for Hot Standby /
>> Streaming Replication in pgAdmin (that was a really small patch, there
>> was not a lot to do)
>
> Well done.
>
>
Le 22/06/2010 12:42, Simon Riggs a écrit :
> On Tue, 2010-06-22 at 12:19 +0200, Guillaume Lelarge wrote:
>> Shamely simple : I only added some informations on the server's
>> properties. See
>> http://www.pgadmin.org/images/visualtour12/visualtour08.jpg. We only
>>
Le 22/06/2010 06:40, Takahiro Itagaki a écrit :
> [...]
> Tom Lane wrote:
>
>> I'm of the opinion that this is a 9.1 problem. It needs more thought
>> than we can put into it now --- one obvious question is what about
>> monitoring on the slave side? Another is who should be able to see the
>>
Hi,
Today, I tried to cancel the change of a tablespace for a table (ALTER
TABLE ... SET TABLESPACE). I got the "Cancel request sent" but the query
continued and finally succeed. It was a big issue for my customer, and I
wanted to look more into that issue. So, I got a look at the source code
and
Le 31/01/2010 17:35, Tom Lane a écrit :
> Guillaume Lelarge writes:
>
>> */
>> do
>> {
>> + const char *values[] = {
>> + my_opts->hostname,
>> + my_opts->port,
>> +
Le 31/01/2010 13:39, Magnus Hagander a écrit :
> On Sun, Jan 31, 2010 at 09:34, Guillaume Lelarge
> wrote:
>> Hi,
>>
>> I worked on a patch to make PostgreSQL binaries use the new
>> PQconnectdbParams() libpq functions. I tried to mimic the way Joe Conway
>>
Hi,
I worked on a patch to make PostgreSQL binaries use the new
PQconnectdbParams() libpq functions. I tried to mimic the way Joe Conway
changed my previous patch.
I know I'm way over the deadline for this commitfest. I couldn't do it
before because my previous patch (on this commit fest) propose
Le 28/01/2010 07:32, Joe Conway a écrit :
> On 01/26/2010 02:55 PM, Guillaume Lelarge wrote:
>> Le 26/01/2010 19:43, Joe Conway a écrit :
>>> On 01/25/2010 03:21 PM, Guillaume Lelarge wrote:
>>>> I didn't put any documentation before knowing which one will be cho
Le 26/01/2010 19:43, Joe Conway a écrit :
> On 01/25/2010 03:21 PM, Guillaume Lelarge wrote:
>> I didn't put any documentation before knowing which one will be choosen.
>> So we still need to work on the manual.
>
> Please send the documentation as a separate patch.
Le 26/01/2010 00:04, Joe Conway a écrit :
> I'm reviewing the patch posted here:
> http://archives.postgresql.org/pgsql-hackers/2010-01/msg01579.php
> for this commitfest item:
> https://commitfest.postgresql.org/action/patch_view?id=259
>
First, thanks for reviewing my patch.
> Patch attach
Le 24/01/2010 06:06, Jaime Casanova a écrit :
> On Sat, Jan 23, 2010 at 10:08 PM, Robert Haas wrote:
>>
>> I was also thinking about the possibility of adding a new option
>> called "output" and making that control whether the "Output" line gets
>> printed. It's kind of annoying to use EXPLAIN (A
Le 15/01/2010 18:53, Guillaume Lelarge a écrit :
> Le 08/01/2010 23:22, Guillaume Lelarge a écrit :
>> Le 07/01/2010 19:13, Robert Haas a écrit :
>>> On Thu, Jan 7, 2010 at 10:33 AM, Guillaume Lelarge
>>> wrote:
>>>> Le 04/01/2010 22:36, Guillaume Lela
Le 08/01/2010 23:22, Guillaume Lelarge a écrit :
> Le 07/01/2010 19:13, Robert Haas a écrit :
>> On Thu, Jan 7, 2010 at 10:33 AM, Guillaume Lelarge
>> wrote:
>>> Le 04/01/2010 22:36, Guillaume Lelarge a écrit :
>>>> Le 29/12/2009 14:12, Guillaume Lelarge
Le 07/01/2010 19:13, Robert Haas a écrit :
> On Thu, Jan 7, 2010 at 10:33 AM, Guillaume Lelarge
> wrote:
>> Le 04/01/2010 22:36, Guillaume Lelarge a écrit :
>>> Le 29/12/2009 14:12, Guillaume Lelarge a écrit :
>>>> Le 29/12/2009 00:03, Guillaume Lelarge a écrit
Le 04/01/2010 22:36, Guillaume Lelarge a écrit :
> Le 29/12/2009 14:12, Guillaume Lelarge a écrit :
>> Le 29/12/2009 00:03, Guillaume Lelarge a écrit :
>>> Le 28/12/2009 22:59, Tom Lane a écrit :
>>>> Guillaume Lelarge writes:
>>>>> Le 28/12/2009 17:
Le 29/12/2009 14:12, Guillaume Lelarge a écrit :
> Le 29/12/2009 00:03, Guillaume Lelarge a écrit :
>> Le 28/12/2009 22:59, Tom Lane a écrit :
>>> Guillaume Lelarge writes:
>>>> Le 28/12/2009 17:06, Tom Lane a écrit :
>>>>> I think we were stalle
Le 29/12/2009 00:03, Guillaume Lelarge a écrit :
> Le 28/12/2009 22:59, Tom Lane a écrit :
>> Guillaume Lelarge writes:
>>> Le 28/12/2009 17:06, Tom Lane a écrit :
>>>> I think we were stalled on the question of whether to use one array
>>>> or two parall
Le 28/12/2009 22:59, Tom Lane a écrit :
> Guillaume Lelarge writes:
>> Le 28/12/2009 17:06, Tom Lane a écrit :
>>> I think we were stalled on the question of whether to use one array
>>> or two parallel arrays. Do you want to try coding up a sample usage
>>&g
Le 28/12/2009 17:06, Tom Lane a écrit :
> Guillaume Lelarge writes:
>> Le 28/12/2009 10:07, Dave Page a écrit :
>>> Yes, still waiting on the new API.
>
>> Is there something I can do to make this move forward?
>
> I think we were stalled on the question of
Le 28/12/2009 10:07, Dave Page a écrit :
> On Sun, Dec 27, 2009 at 11:15 PM, Guillaume Lelarge
> wrote:
>> Le 13/11/2009 12:11, Dave Page a écrit :
>>> [...]
>>>> What about pg_dump/psql setting fallback_application_name?
>>>
>>> Per Tom, I'
Le 13/11/2009 12:11, Dave Page a écrit :
> [...]
>> What about pg_dump/psql setting fallback_application_name?
>
> Per Tom, I'm waiting on the possible new array-based libpq connect API
> which will make a conversion of those utilities from PQsetdbLogin a
> lot cleaner than moving to PQconnectdb (
Le 18/12/2009 18:07, Tom Lane a écrit :
> On current Fedora 11, there is a huge difference in initdb time if you
> have TZ set versus if you don't: I get about 18 seconds versus less than
> four.
>
> $ time initdb
> ... blah blah blah ...
>
> real0m17.953s
> user0m6.490s
> sys 0m10.93
Le mardi 15 décembre 2009 à 06:30:15, Greg Smith a écrit :
> [...]
> > BTW, this list is listed as the list for tech questions in the pgAdmin
> > tips, therefore if you don't want to be disturb, you might want to
> > remove it from the pgAdmin tips.
>
> When I look at http://www.pgadmin.org/suppor
Le jeudi 19 novembre 2009 à 23:05:16, Peter Eisentraut a écrit :
> On tor, 2009-11-19 at 16:47 +0100, Guillaume Lelarge wrote:
> > "pg_restore --help" gives this message for the --no-tablespaces
> > parameter:
> >
> > --no-tablespaces do not du
1 - 100 of 153 matches
Mail list logo
