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 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
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
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,
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,
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
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.
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 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,
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
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
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
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
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
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
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
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
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 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.
>
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 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
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 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 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 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 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 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 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
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 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 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
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
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
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-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-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
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 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
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 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 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
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
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 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
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
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:
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
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
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
>>
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-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
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-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
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 :
>>
>>>
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
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 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
>>
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 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 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 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 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 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 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 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 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 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 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
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
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
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 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 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
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 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
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
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
Dave Page a écrit :
Hi Michael,
Looks like your latest commit fixed the problem. Thanks for working on it.
But it breaks 8.2 and 8.1 branches. See
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=kite&dt=2007-05-21%2007:47:01.
I've send a patch on pgsql-patch that fixes it.
Regards.
--
Jim C. Nasby a écrit :
On Fri, Jul 13, 2007 at 01:45:18PM -0700, Joshua D. Drake wrote:
Jim C. Nasby wrote:
According to http://developer.postgresql.org/index.php/Feature_Matrix,
8.2 has non-blocking CREATE INDEX, which is news to me. Is it correct?
CREATE INDEX CONCURRENTLY
Well, I guess it
Andrew Dunstan a écrit :
>
>
> Albert Cervera i Areny wrote:
>>> I'm very strongly in favor of having this documentation. However, I
>>> think
>>> it might make sense to put "Contrib Modules" as a section under either
>>> "Reference" or "Appendices". Also, I don't think it's necessary to make
>
korry.douglas a écrit :
> Now that we've "announced" (see
> http://www.informationweek.com/news/showArticle.jhtml?articleID=201803375&subSection=News)
> that 8.3 will include a debugger (don't worry, it's a PL/pgSQL debugger
> :-), has anyone actually tried it yet (other than myself and Dave Page)?
Tom Lane a écrit :
> Bruce Momjian <[EMAIL PROTECTED]> writes:
>> Alvaro Herrera wrote:
>>> Does this mean that if I commit something in these days to those
>>> branches, it will not show up in the releases?
>
>> It certainly will show up if you do it before the packagers pull their
>> CVS copies.
Dave Page a écrit :
> Guillaume Lelarge wrote:
>> Tom Lane a écrit :
>>> Bruce Momjian <[EMAIL PROTECTED]> writes:
>>>> Alvaro Herrera wrote:
>>>>> Does this mean that if I commit something in these days to those
>>>>> branches, i
Tom Lane a écrit :
> Dave Page <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote:
>>> Peter usually does it --- in theory any committer could, but he actually
>>> knows what to do and the rest of us would have to study ;-)
>
>> Study or figure it out? If it hasn't already been it should be
>> documen
Magnus Hagander a écrit :
> On Thu, Sep 13, 2007 at 12:12:28AM +0200, Guillaume Lelarge wrote:
>> [...]
>> It seems pretty straightforward now. Perhaps it can be used with cron.
>
> No. Doing that with cron is a really bad idea, imho. We do *not* want any
> automated com
Hi,
I wonder why all messages going through errcontext function are not
translatable. I found this when working on PL/pgsql but it seems other
functions (like COPY, see backend/commands/copy.c) call errcontext and
none propose translatable messages.
Can I send a patch so we can translate them ?
Tom Lane a écrit :
Guillaume Lelarge <[EMAIL PROTECTED]> writes:
I wonder why all messages going through errcontext function are not
translatable.
I don't think it's errcontext's fault. The PLs in general don't have
any translation coverage. This seems a bit diffi
Alvaro Herrera a écrit :
> Peter Eisentraut wrote:
>> Do we care to maintain a maximum width for programs' --help output (and
>> psql's
>> \?)? I think 79 characters was once a recommendation (or perhaps 72), but
>> we
>> have a couple of violations either way, which I'd like to fix, but what
Hi,
First, I'm not sure this mail should go to this mailing list. As it
refers to source code (mainly src/backend/postmaster/bgwriter.c and
src/backend/access/transam/xlog.c), I sent it here. I apologize if I'm
wrong.
I'm a bit puzzled by the different informations I can read on the
documentation
Tom Lane a écrit :
> Guillaume Lelarge <[EMAIL PROTECTED]> writes:
>> I try to answer a simple question : what happens when I do a simple
>> "INSERT" on a just started PostgreSQL server.
>
>> From what I understand with the INSERT statement, here is what
Alvaro Herrera a écrit :
> Guillaume Lelarge wrote:
>> Tom Lane a écrit :
>>> Guillaume Lelarge <[EMAIL PROTECTED]> writes:
>>>> I try to answer a simple question : what happens when I do a simple
>>>> "INSERT" on a just started Post
Hi all,
I'm not sure psql handles \dFp the right way. The query allows
translators to translate some columns' values but forgets to escape the
strings. So, here is a patch that escapes these translated strings.
Regards.
--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com
Index: src/b
Tom Lane a écrit :
> Guillaume Lelarge <[EMAIL PROTECTED]> writes:
>> I'm not sure psql handles \dFp the right way. The query allows
>> translators to translate some columns' values but forgets to escape the
>> strings. So, here is a patch that escapes thes
Tom Lane a écrit :
> Guillaume Lelarge <[EMAIL PROTECTED]> writes:
>> Tom Lane a écrit :
>>> This seems mighty ugly, and it's not the way we handle any other \d
>>> command. Why is it needed for \dFp (and only that)?
>
>> The problem here is
Alvaro Herrera wrote:
Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
I suggest
cannot execute \"%s\" on \"%s\" because ...
Hmm, why not just
cannot execute %s \"%s\" because ...
?
Hmm, yeah, that seems fine too. Thinking more about it, from the POV of
the tra
Alvaro Herrera a écrit :
[...]
For those that think that the \du output is currently OK because it
doesn't wrap, consider the french translation which is quite a bit wider
than the original:
alvherre=# \du
Liste des rôles
Nom du rôle | Superutilisateur | Cr
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 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 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 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'
1 - 100 of 153 matches
Mail list logo
