more
than or equal to 8192.
Thanks for the review, please find the latest patch attached in the mail.
Regards,
Hari babu.
pglz-with-micro-optimization-compress-using-newdata-3.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.o
On Monday, July 08, 2013 5:16 PM Andres Freund wrote:
>On 2013-07-08 17:10:43 +0530, Amit Kapila wrote:
>> On Monday, July 08, 2013 4:26 PM Andres Freund wrote:
>> > On 2013-07-08 16:17:54 +0530, Hari Babu wrote:
>> > > +This utility can also be used to decide w
On Friday, July 05, 2013 6:48 PM Hari Babu wrote:
>On Thursday, July 04, 2013 11:19 PM Robert Haas wrote:
The patch is updated with the following changes.
1.If the input data is data directory, all the errors occurred are displayed
at once instead of one error at a time.
2.Fixed the problem
etails.
Src/backend/access/transam/
Regards,
Hari babu.
iple file or directories parsing and printing
Max LSN for each input argument.
>I think the documentation should say something about the intended uses
>of this tool, including cautions against using it for things to which
>it is not well-suited. I guess the threshold question for this patch
&
se the environment
variable
>+PGDATA.
>Same thing here. I think using PGDATA would be quite appropriate for
>this utility.
Fixed.
>+
>+This command must not be used when the server is
>+running. pg_computemaxlsn will refuse to start up
if
>+it finds a ser
On June 26, 2013 5:02 AM Josh Kupershmidt wrote:
>Thanks for the feedback. Attached is a rebased version of the patch with
the two small issues noted fixed.
Patch is good, I marked the patch as ready for committer.
Regards,
Hari babu
--
Sent via pgsql-hackers mailing list (pgsql-hack
ing_quote + 1) !=
'\0') {
where it's exact usage is present.
Testing:
I tested this feature with different postmaster options and database folder
names, found no problem.
The database folder with quotes present in it is any way having problems
with pg_ctl.
I feel th
?
ev_attr - The column this rule is for, presently this value is -1.
Regards,
Hari babu.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Monday, February 18, 2013 8:06 PM Boszormenyi Zoltan wrote:
>On 2013-01-29 11:15 keltezéssel, Magnus Hagander írta:
>> On Thu, Jan 24, 2013 at 7:04 AM, Hari Babu wrote:
>>> On Wed, Jan 23, 2013 11:48 PM, Magnus Hagander wrote:
>>>> On Wed, Jan 23, 2013 at 10:18 A
On Wednesday, January 30, 2013 7:59 PM Zoltán Böszörményi wrote:
>>2013-01-28 15:20 keltezéssel, Hari Babu írta:
>> 2. regress check failed because the expected ".out" file is not
>> updated properly.
>
>Which regress check failed? The .out file was updated i
he patch:
1. Patch needs a rebase as it causing some rejections.
2. regress check failed because the expected ".out" file is not updated
properly.
Regards,
Hari babu.
lock_timeout_test.sql
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgre
On Tue, Jan 22, 2013 3:27 PM Hari Babu wrote:
>On Saturday, January 19, 2013 5:49 PM Magnus Hagander wrote:
>>On Fri, Jan 18, 2013 at 1:05 PM, Heikki Linnakangas
>> wrote:
>>> On 18.01.2013 13:41, Amit Kapila wrote:
>>>>
>>>> On Friday, J
On Wed, Jan 23, 2013 11:48 PM, Magnus Hagander wrote:
>On Wed, Jan 23, 2013 at 10:18 AM, Hari Babu
wrote:
>> Test scenario to reproduce:
>> 1. Start the server
>> 2. create the user as follows
>> ./psql postgres -c "create user u
asebackup -D ../../data1 -R -U user1 -W
The following errors are occurring when the new standby on the backup
database starts.
FATAL: could not connect to the primary server: missing "=" after "1'" in
connection info string
Regards,
Hari babu.
--
Sent via pgsql-hack
impler, the connection string is formed inside with the
existing
command line options, if the user is not provided the "connection_string"
option.
which is used for further processing.
2. The connection_string and existing command line options are handled
separately.
I feel approach-1
On January 07, 2013 7:53 PM Boszormenyi Zoltan wrote:
>Since my other patch against pg_basebackup is now committed,
>this patch doesn't apply cleanly, patch rejects 2 hunks.
>The fixed up patch is attached.
Patch is verified. Thanks for rebasing the patch.
Regards,
Hari babu.
On January 02, 2013 12:41 PM Hari Babu wrote:
>On January 01, 2013 10:19 PM Boszormenyi Zoltan wrote:
>>I am reviewing your patch.
>> Is the patch in context diff format?
>>Yes.
>
>Thanks for reviewing the patch.
>
>> Does it apply cleanly to the current gi
7;)
> {
> int pos;
>***
>
>Other comments are sufficient and accurate.
I will fix and update the patch.
Please let me know if anything apart from above needs to be taken care.
Regards,
Hari babu.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
it seems possibly useful for other purposes as
well.
Regards,
Hari babu.
On Thu, Dec 7, 2012 at 7:56 PM, Hari babu
wrote:
>>On Thu, Dec 6, 2012 at 8:52 PM, Merlin Moncure wrote:
>>Thanks for that -- that's fairly comprehensive I'd say. I'm quite
>>interested in that benchmarking framework as well. Do you need help
>>s
heckpoint;
I will provide the test results later.
Any suggestions/comments?
Regards,
Hari babu.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
> On Wed, Nov 28, 2012 at 12:43 PM, Michael Paquier <
michael(dot)paquier(at)gmail(dot)com>wrote:
>> On Wed, Nov 28, 2012 at 3:55 PM, Hari Babu
wrote:
>> pg_basebackup is taking backup of extra files other than database related
>> files in side a TABLESPACE directory.
r "Linkpath/TABLESPACE_VERSION_DIRECTORY "
as path.
Regards,
Hari babu.
ster.pid", O_RDONLY, 0)) < 0)
{
if (errno != ENOENT)
{
Any suggestions/comments?
Regards,
Hari babu.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
25 matches
Mail list logo
