it ;) )
An example where using isatty() might fail is if you run pg_basebackup
from a tty but redirect the output to a file, I believe that in that
case isatty() will return true, but it's very likely that the user
might want batch mode output.
But maybe we should also add Arthurs idea any
further.
--
Martín Marquéshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
constantly run
index checks (query a sample of the data from the heap and from the
index and check they match). In our case, the customer was not aware of
the dups until we found them.
Regards,
--
Martín Marquéshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Suppo
comments about maybe this being the cause of old
reports about index corruption.
I ask myself if it's a good idea to make a point release with a know
corruption bug in it.
Regards,
--
Martín Marquéshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Trainin
parameters, so this makes total sense.
I will have a better check at the patch and get back (didn't find
anything wrong at the first look at it).
Regards,
--
Martín Marquéshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent vi
2016-08-30 2:02 GMT-03:00 Michael Paquier :
> On Tue, Aug 30, 2016 at 5:43 AM, Martín Marqués
> wrote:
>> This is v4 of the patch, which is actually a cleaner version from the
>> v2 one Michael sent.
>>
>> I stripped off the external index created from the tests
duplicated.
I think this patch is a very good first approach. Future improvements
can be made for indexes, but we need to get the extension dependencies
right first. That could be done later, on a different patch.
Thoughts?
--
Martín Marquéshttp://www.2ndQuadrant.com/
PostgreSQL D
end on will not be dumped, so it's the
developer/DB designer who has to take care of these things.
If in the near or not so near future we provide a patch to deal with
these missing dependencies, we can easily patch pg_dump so it deals
with this correctly.
Regards,
--
Martín Marqués
mp_schema.test_index doesn't.
Or is this something we shouldn't support (in that case we should document it).
--
Martín Marquéshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hacker
Hi,
2016-08-26 10:53 GMT-03:00 Martín Marqués :
>
> There's still one issue, which I'll add a test for as well, which is
> that if the index was created by the extension, it will be dumped
> anyway. I'll have a look at that as well.
Looking at this issue today, I foun
Hi,
2016-08-25 8:10 GMT-03:00 Michael Paquier :
> On Thu, Aug 25, 2016 at 10:25 AM, Martín Marqués
> wrote:
>> 2016-08-24 21:34 GMT-03:00 Michael Paquier :
>>>
>>> Yes, you are right. If I look at the diffs this morning I am seeing
>>> the ACLs being dump
r some time, so that's not exclusive to 9.6 :)
Hi Michael,
Do you see any easier way than what I mentioned earlier (adding a
selectDumpableIndex() function) to fix the index dumping issue?
Regards,
--
Martín Marquéshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24
2016-08-24 17:01 GMT-03:00 Martín Marqués :
> 2016-08-24 11:15 GMT-03:00 Stephen Frost :
>> Michael,
>>
>> * Michael Paquier (michael.paqu...@gmail.com) wrote:
>>> The patch attached includes all those tests and they are failing. We
>>> are going to need a pa
lures regarding the CREATE INDEX that Michael
reported but can't quite find where it's originated. (or actually
where the problem is)
--
Martín Marquéshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via
Hi,
2016-08-23 16:46 GMT-03:00 Martín Marqués :
>
> I will add tests for sequence and functions as you mention and test again.
>
> Then I'll check if other tests should be added as well.
I found quite some other objects we should be checking as well, but
this will add some d
Hi Michael,
2016-08-23 5:02 GMT-03:00 Michael Paquier :
> On Sat, Aug 13, 2016 at 6:58 AM, Martín Marqués
> wrote:
>> I believe the fix will be simple after the back and forth mails with
>> Michael, Stephen and Tom. I will work on that later, but preferred to
>> hav
, all expected due to the bug we have
at hand.
I believe the fix will be simple after the back and forth mails with
Michael, Stephen and Tom. I will work on that later, but preferred to
have the tests the show the problem which will also make testing the fix
easier.
Thoughts?
Regards,
--
M
2016-06-21 13:08 GMT-03:00 Robert Haas :
> On Thu, Jun 16, 2016 at 1:46 PM, Martín Marqués
> wrote:
>> The comment is accurate on what is going to be dumpable and what's not
>> from the code. In our case, as the pgq schema is not dumpable becaause
>> it comes from a
Hi,
2016-06-16 9:48 GMT-03:00 Michael Paquier :
> On Thu, Jun 16, 2016 at 8:37 PM, Martín Marqués
> wrote:
>> El 16/06/16 a las 00:08, Michael Paquier escribió:
>>> On Wed, Jun 15, 2016 at 7:19 PM, Martín Marqués
>>> wrote:
>>>>
>>>> How
El 16/06/16 a las 09:48, Michael Paquier escribió:
> On Thu, Jun 16, 2016 at 8:37 PM, Martín Marqués
> wrote:
>
>> This problem came up due to a difference between pg_dump on 9.1.12 and
>> 9.1.22 (I believe it was due to a patch on pg_dump that excluded the
>> d
El 16/06/16 a las 00:08, Michael Paquier escribió:
> On Wed, Jun 15, 2016 at 7:19 PM, Martín Marqués
> wrote:
>>
>> How would the recovery process work? We expect the schema to be there
>> when restoring the tables?
>
> pg_dump creates the schema first via the CR
re some controversy about switching to major.minor versioning
this in -advocacy?
http://www.postgresql.org/message-id/ee13fd2bb44cb086b457be34e81d5...@biglumber.com
IMO, this versioning is pretty good and people understand it well, with
the other will be using postgres 13 by 2020, which isn't fa
+1
And another +1 on Tom's opinion on it being too late after beta1 has
been released.
--
Martín Marquéshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To mak
hange, and how I got
there, and I believe it gives better meaning to the sentence in question.
I applied the same change on another part which had the same phrase.
Cheers,
--
Martín Marquéshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training &
e fact that all LO live in a common
catalog table (pg_largeobjects).
If the LO were stored per-database, with a some alike schema as
pg_largeobjects, then they could be placed on any tablespace available,
and even get dumped on a normal DB dump, which makes administration much
simpler.
Cheers,
cal user ID %ld: %s"
Cheers,
--
Martín Marquéshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
, because silly
changes should be tested as well ;)).
2014-03-07 21:46 GMT-03:00 Martín Marqués :
> I was testing some builds I was doing and found that the regression
> tests fails when doing the against a Hot Standby server:
>
> $ make standbycheck
> [...]
> == runni
#x27;s nice for future testing.
Regards,
--
Martín Marqués http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
regression.diffs
Description: Binary data
From b6db8388e37f6afaa431e31239fd972d10140cc1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mart=C3=ADn=20Ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
El 21/01/14 20:11, Devrim GÜNDÜZ escribió:
>
> Hi,
>
> On Tue, 2014-01-21 at 20:19 -0200, Martín Marqués wrote:
>> I was updating the packages from one of my servers and I got
>> this message:
>>
>> Package py
signed
Something wrong with the packages?
--
Martín Marqués http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mail
El 21/06/13 23:47, Jaime Casanova escribió:
On Fri, Jun 21, 2013 at 8:56 PM, Martín Marqués wrote:
When ever I try to see the patch from this commit it never loads:
https://commitfest.postgresql.org/action/patch_view?id=1129
Some problem there? I can see other patches, from other commits
When ever I try to see the patch from this commit it never loads:
https://commitfest.postgresql.org/action/patch_view?id=1129
Some problem there? I can see other patches, from other commits.
--
Martín Marquéshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support
El Mié 27 Jul 2005 18:23, Alvaro Herrera escribió:
> On Wed, Jul 27, 2005 at 06:05:26PM -0300, Martín Marqués wrote:
> >
> > Will there be a way to ballance the amount of stats the autovacuum gets?
> > Something like the analyze parameters that the contrib version has, b
nvolved the time reduced
dramatically.
Running on a 8.0.3 server with autovacuum running every 5 minutes.
--
17:52:04 up 25 days, 2:37, 1 user, load average: 0.90, 1.00, 0.97
---------
Lic. Martín Marqués | SELECT 'mmarques' ||
Centro de Te
(with no Postgres on the
> system), build Postgres and then build DBD::Pg as a completely
> separate step.
The same thing can be done with PHP.
--
09:25:38 up 3 days, 17:54, 1 user, load average: 0.45, 0.28, 0.38
-
Mar
, IMHO.
--
09:03:26 up 3 days, 17:32, 1 user, load average: 0.39, 0.61, 0.64
---------
Martín Marqués| select 'mmarques' || '@' || 'unl.edu.ar'
Centro de Telematica | DBA, Progr
running, nothing else to do.
Tom, could you give a small insight on what occurred here, why those 8k of zeros
fixed it, and what is a "WAL replay"?
I am very curious about it.
--
select 'mmarques' || '@' || 'unl.edu.ar' AS email;
--
man pages as we speak!
# dd if=/dev/zeros of=somefile
# cat file1 somefile >> newfile
# mv newfile file1
file1 is "/usr/local/pgsql/data/pg_clog/000D"
--
select 'mmarques' || '@' || 'unl.edu.ar' AS email;
-
-
PostgreSQL 7.1.3 on sparc-sun-solaris2.7, compiled by GCC 2.95.2
TIA!
--
Porqué usar una base de datos relacional cualquiera,
si podés usar PostgreSQL?
-
Martín
of 142 inserts that didn't get the second insert of the
rule to go.
The question is why is this happening, and how can I fix it?
If you need logs or something, I have no problem at all.
Saludos... :-)
--
Porqué usar una base de datos relacional cualquiera,
si podés usar PostgreSQL?
-
h.
Is there some logic?
TIA!
--
Porqué usar una base de datos relacional cualquiera,
si podés usar PostgreSQL?
-
Martín Marqués |[EMAIL PROTECTED]
Programador, Administrador, DBA | Centro de Tele
Saludos... :-)
--
Porqué usar una base de datos relacional cualquiera,
si podés usar PostgreSQL?
-----
Martín Marqués |[EMAIL PROTECTED]
Programador, Administrador, DBA | Centro de Te
can we trust a RC version?
Saludos... :-)
--
Porqué usar una base de datos relacional cualquiera,
si podés usar PostgreSQL?
-
Martín Marqués |[EMAIL PROTECTED]
Programador, Administrador, DBA | Cen
have to change the permission by hand.
Has this already been reported?
saludos... :-)
--
Porqué usar una base de datos relacional cualquiera,
si podés usar PostgreSQL?
-
Martín Marqués |[EMAIL PROTECTED
--
Porqué usar una base de datos relacional cualquiera,
si podés usar PostgreSQL?
---------
Martín Marqués |[EMAIL PROTECTED]
Programador, Administrador, DBA | Centro de Telematica
Uni
e past chunk end in TransactionCommandContext
3aadf0
Any idea? Some databases are screwed up
Saludos... :-)
--
Porqué usar una base de datos relacional cualquiera,
si podés usar PostgreSQL?
-
Martín Marqués
és usar PostgreSQL?
---------
Martín Marqués |[EMAIL PROTECTED]
Programador, Administrador, DBA | Centro de Telematica
Universidad Nacional
On Thursday 05 April 2001 00:41, Thomas Lockhart wrote:
> I've got patches for the regression tests to work around the "time with
> time zone" DST problem. Will apply to the tree asap, and will post a
> message when that is done.
Is RC3 going out or should I think about RC2?
Saludos... ;-)
--
On Wednesday 04 April 2001 22:42, Ciaran Johnston wrote:
> Hi,
>
> Sorry to bother you's but I am currently doing a database comparison and
> have been trying to get postgresql installed. I'm running Solaris 2.7. I
> downloaded pgsql 7.03 and ran ./configure in the src/ directory. This
> was fine
On Wednesday 04 April 2001 13:29, Pete Forman wrote:
> > Solaris 2.7-8 Sparc7.1 2001-03-22, Marc Fournier
>
> I've reported Solaris 2.6 Sparc as working on a post-RC1 snapshot.
Same for Solaris 8 Sparc, but only tested with RC1.
--
El mejor sistema operativo es aquel que te da de comer.
Cu
I'm at the moment installing Postgresql-7.1RC1 on Solaris 7 and 8 over
UltraSPARC.
What do I have to do to report a regression test?
Where should I look for info on this.
Saludos... :-)
--
El mejor sistema operativo es aquel que te da de comer.
Cuida tu dieta.
-
51 matches
Mail list logo
