On Tue, 2017-12-12 at 18:10 -0500, jonathan vanasco wrote:
> I have table where the primary key is a sequence. I was getting a lot of
> errors on insertions,
> and noticed the current value was around 65k, but the max id in the database
> was around 160k.
> everything works now that i've restart
Dear Thomas and All,
Thanks for sharing your input.
How we calculate
autovacuum_multixact_freeze_max_age paramter limit into system?
Regards,
Yogesh
On Wednesday, December 13, 2017, Thomas Munro
wrote:
> On Wed, Dec 13, 2017 at 5:05 AM, David G. Johnston
> wrote:
> > On Tue, Dec 12, 2017 at 2
I can't figure out how this happened
I have table where the primary key is a sequence. I was getting a lot of
errors on insertions, and noticed the current value was around 65k, but the max
id in the database was around 160k. everything works now that i've restarted
it, but I can't find any
Hi All,
Postgres 9.6.5. We run several logical replication processes off our main
postgres server. What we've noticed is that schema changes seem to block
until we halt the logical replication processes. For example, I just did a
'DROP INDEX CONCURRENTLY' command, and it just sat there until I sto
On Mon, Dec 11, 2017 at 12:07 PM, Jeff Janes wrote:
> On Tue, Dec 5, 2017 at 5:50 PM, Thomas Munro
> wrote:
>> The problem is that our logic (1) focuses on when we should *start*
>> freezing, not by when we'd like to be finished, and (2) is defined in
>> such a way that many tables are likely to
On 12 December 2017 at 02:38, Jim Finnerty wrote:
> If necessary, the planner could also check that the FK constraint is not
> DEFERRED, but if there are no volatile functions and the SELECT statement
> can't see an inconsistent state created by any other transaction, I think
> that just checking
On Wed, Dec 13, 2017 at 5:05 AM, David G. Johnston
wrote:
> On Tue, Dec 12, 2017 at 2:52 AM, Yogesh Sharma
> wrote:
>>
>> Dear All,
>>
>> I am using PostgreSQL 9.3.6 version and PGDATA pg_multixact.members folder
>> size is increased to around 3GB. How to reduce this folder size and how to
>> fi
On Tue, Dec 12, 2017 at 5:18 AM, John McKown
wrote:
> On Tue, Dec 12, 2017 at 2:17 AM, Tsunakawa, Takayuki
> wrote:
>>
>> Hi Laurenz, Tom, Peter,
>>
>> Thanks for your suggestions. The practical solution seems to be to
>> override comparison operators of char, varchar and text data types with UD
On Tue, 12 Dec 2017 07:18:10 -0600, John McKown
wrote:
>?This is a guess on my part, based on many years on an EBCDIC system. But
>I'll bet that they are doing a conversion off of the EBCDIC system (maybe
>Db2 on z/OS) to an ASCII system (Linux or Windows) running PostgreSQL. They
>want to be abl
Hi,
On Thu, 2017-12-07 at 11:29 +, Kaliappa, Karthic wrote:
> We are looking to upgrade our application from postgres 9.5 to 10x, but we
> are unable to find the RPM named 'pg_catcheck-10x' for Redhat: https://downl
> oad.postgresql.org/pub/repos/yum/10/redhat/rhel-6.7-x86_64/
> We request y
If that's the case, I wonder if OP could write a function that would
convert from the ASCII code-point ot the EBCDIC codepoint. For instance,
(using the function at https://wiki.postgresql.org/wiki/Binary_Replace)
convert A to char 193, `select binary_replace('Anne'::bytea, 'A'::bytea,
'\xc1'::byte
On Tue, Dec 12, 2017 at 2:52 AM, Yogesh Sharma
wrote:
> Dear All,
>
> I am using PostgreSQL 9.3.6 version and PGDATA pg_multixact.members folder
> size is increased to around 3GB. How to reduce this folder size and how to
> fix this issue?
> Is it realted to poatgres issue? If yes how to reprodu
Please share direction to resolve below issue.
Regards,
Yogesh
On Tuesday, December 12, 2017, Yogesh Sharma wrote:
> Dear All,
>
> I am using PostgreSQL 9.3.6 version and PGDATA pg_multixact.members folder
> size is increased to around 3GB. How to reduce this folder size and how to
> fix this
On Tue, Dec 12, 2017 at 9:43 AM, James Keener wrote:
> Sorry for spamming the list. It appears that I'm an idiot. Sorry :(
>
I guess we're even now. We both made a similar mistake.
But, despite my error, I still think the OP's need for an EBCDIC order is
to compare output from parallel runs
Sorry for spamming the list. It appears that I'm an idiot. Sorry :(
jim=# select * from test order by a collate "C";
a
--
12 Days of Christmas
12 drummers
Anne
Isaac
Jim
a
aardvark
b
island
job
(10 rows)
jim=# select * from test order by a collate "en_US.ut
en_US.utf8. is still 0-9A-Za-z and in my example set (as it's my default
too :))
You'd need a case insensitive collation to do what you described, and I'm
not sure those exist in postgres. (I guess you could always build your own
if you _really_ wanted to.
Jim
On Tue, Dec 12, 2017 at 10:24 AM, J
On Tue, Dec 12, 2017 at 9:11 AM, James Keener wrote:
> The default C locale on Linux (I don't know Windows) will sort "digits",
>> then alphabetic with the lower then upper case of each letter in order
>> like: "aAbB...zZ"
>>
>
> That's no true at all! The C locales are 0-9A-Za-z
>
Thanks for t
>
> The default C locale on Linux (I don't know Windows) will sort "digits",
> then alphabetic with the lower then upper case of each letter in order
> like: "aAbB...zZ"
>
That's no true at all! The C locales are 0-9A-Za-z
#include
> #include
> #include
> #include
> #include
>
>
> static int
On Tue, Dec 12, 2017 at 2:17 AM, Tsunakawa, Takayuki <
tsunakawa.ta...@jp.fujitsu.com> wrote:
> Hi Laurenz, Tom, Peter,
>
> Thanks for your suggestions. The practical solution seems to be to
> override comparison operators of char, varchar and text data types with
> UDFs that behave as Tom mentio
Em 12/12/2017 10:14, marcelo escreveu:
Hi Sam
You are right, and here are the reason behind my question: The server
where postgres will be installed is not on 24/7. It turns on in the
morning and goes off at the end of the day. The idea is that, as part
of the shutdown process, a local backup
On Tue, Dec 12, 2017 at 07:40:46AM -0500, Adam Tauno Williams wrote:
> > The next day, that backup will be copied to the cloud.
>
> What does this mean? If it is rsync of a local dump to a remote use
> the directory dump format - disable compression - then each table which
> didn't change will '
> The next day, that backup will be copied to the cloud.
What does this mean? If it is rsync of a local dump to a remote use
the directory dump format - disable compression - then each table which
didn't change will 'copy' almost instantly.
--
Meetings Coordinator, Michigan Association of Railr
Hi Sam
You are right, and here are the reason behind my question: The server
where postgres will be installed is not on 24/7. It turns on in the
morning and goes off at the end of the day. The idea is that, as part of
the shutdown process, a local backup is made. The next day, that backup
wil
Il 11/12/2017 14:37, Vincent Veyron ha scritto:
On Sat, 9 Dec 2017 10:11:42 -0600
Dale Seaburg wrote:
No Go! Would not start.
Any error message in your logs?
I would certainly second Scott's suggestion to check the processors. I've had
to do what you describe once, and it took me four m
Dear All,
I am using PostgreSQL 9.3.6 version and PGDATA pg_multixact.members folder
size is increased to around 3GB. How to reduce this folder size and how to
fix this issue?
Is it realted to poatgres issue? If yes how to reproduce this issue?
Thanks in advance.
Regards,
Yogesh
Hi Laurenz, Tom, Peter,
Thanks for your suggestions. The practical solution seems to be to override
comparison operators of char, varchar and text data types with UDFs that behave
as Tom mentioned.
From: Peter Geoghegan [mailto:p...@bowt.ie]
> That said, the idea of an "EBCDIC collation" seems
26 matches
Mail list logo
