> >
> Hmm...
>
> 2 4 6 8 10
>
> 3 6
>
> 5 10
>
> Adding a prime as an increment is not sufficient to guarantee uniqueness!
>
> You have to ensure that the product of the 2 smallest primes you use
> is greater than any number you'd need to generate. With such large
> primes you may run out of
On Thu, Sep 14, 2017 at 07:11:19PM +0200, Rafal Pietrak wrote:
>
> As I said, I'm not looking for performance or "fair probability" of
> planetary-wide uniqueness.
>
> My main objective is the "guarantee". Which I've tried to indicate
> referring to "future UPDATEs".
>
> What I mean here is func
On Tue, May 30, 2017 at 09:14:41PM +0200, Ludovic Vaugeois-Pepin wrote:
> I ran into the issue described below with 10.0 beta. The error I got is:
>
> pg_basebackup: could not create temporary replication slot
> "pg_basebackup_2194": ERROR: replication slot "pg_basebackup_2194"
> already exists
>
On Thu, Jan 19, 2017 at 03:29:34PM +1100, Venkata B Nagothi wrote:
> On Thu, Jan 19, 2017 at 6:17 AM, PAWAN SHARMA
> wrote:
>
> > Hello All,
> >
> > I am using postgres 9.5 enterprise edition.
> >
> > i want to to how to migrate Sql Server database to PostgreSql. what are
> > the things required
On Fri, Dec 16, 2016 at 09:15:51AM -0500, Bill Moran wrote:
>
> Does anyone have experience using pg_repack on Postgres versions > 9.4?
> Specifically 9.5, but probably 9.6 at some point.
>
> The documentation claims it supports up to 9.4. I haven't looked at it
> closely enough to guess whether
On Tue, Oct 04, 2016 at 07:46:48PM +, Shaun McCready wrote:
> Hello,
>
> I'm having an issue with using the new UPSERT feature in Postgres 9.5
>
> I have a table that is used for aggregating data from another table. The
> composite key is made up of 20 columns, 10 of which can be nullable.
>
On Wed, Aug 31, 2016 at 06:06:54PM +0200, Nicolas Grilly wrote:
> On Wed, Aug 31, 2016 at 6:05 PM, Kenneth Marshall wrote:
>
> > We just run it via cron. In our case, we run it once a day, but depending
> > on
> > your churn, it could be run once a week or more.
> &g
On Wed, Aug 31, 2016 at 05:23:50PM +0200, Nicolas Grilly wrote:
> On Tue, Aug 30, 2016 at 8:17 PM, Kenneth Marshall wrote:
>
> > We have been using the extension pg_repack to keep a table groomed into
> > cluster order. With an appropriate FILLFACTOR to keep updates on the
On Tue, Aug 30, 2016 at 07:51:58PM +0200, Nicolas Grilly wrote:
> On Tue, Aug 30, 2016 at 7:26 PM, Vick Khera wrote:
>
> > I'll assume you have an index on the tenant ID. In that case, your
> > queries will be pretty fast.
> >
> > On some instances, we have multi-column indexes starting with the
On Wed, Aug 03, 2016 at 08:40:26AM -0300, Edson F. Lidorio wrote:
> Good Morning,
>
> Constantly my Postgresql is inaccessible, recording the following
> message in the log.
> I'm using Windows 8.1 and PostgreSQL 9.5
>
>
> 2016-08-02 17:05:59 BRT FATAL: the database system is starting up
> 2016
On Thu, Apr 29, 2010 at 01:13:40PM -, sandeep prakash dhumale wrote:
> Hello All,
>
> I am trying to get tsearch working for my application but I am facing a
> problem when alphabet 'Y' is the in the tsquery.
>
> can anyone please share some light on it.
>
>
> # SELECT 'hollywood'::tsvector
On Wed, Jan 21, 2009 at 03:07:13PM +, Grzegorz Ja??kiewicz wrote:
> On Wed, Jan 21, 2009 at 3:02 PM, paulo matadr wrote:
> > My system have very large ram size, so its possible review postgresql.conf ?
> >
> all depends on how you access DB, what type of drivers (odbc, libpq, etc,
> etc).
> S
On Wed, Jan 21, 2009 at 02:09:01PM +, Grzegorz Ja??kiewicz wrote:
> On Wed, Jan 21, 2009 at 2:06 PM, Kenneth Marshall wrote:
>
> > The TOAST implementation however only allows 30-bits for the
> > size of the TOAST entry which caps the size at 2^30 or 1GB. I
> > agree
On Wed, Jan 21, 2009 at 01:55:28PM +, Grzegorz Ja??kiewicz wrote:
> there's no real limit (its size is described with 32bit number, and
> that's the only limitation here).
> But you need to be aware, that content is sent over at once, so memory
> is the limit in your case.
>
> http://www.postg
On Wed, Jan 21, 2009 at 05:21:03AM -0800, paulo matadr wrote:
> I everyone, need help!!!
> My aplication return erro:
>
> 2009-01-20 10:22:03,264 INFO [STDOUT] Caused by: org.postgresql.util.
> PSQLException: ERROR: invalid memory alloc request size 1705447581
>
> TABLE batch.relatorio_gerado
>
Pretty neat. It may be a possible alternative to the use of
the hash index in some applications.
Cheers,
Ken
On Sun, Feb 03, 2008 at 07:13:23PM -0800, Gurjeet Singh wrote:
> Hi All,
>
> I have wanted to create a reverse key index for some time now, and it
> seems that an evening of reading a
On Mon, Jan 22, 2007 at 07:24:20PM +, Heikki Linnakangas wrote:
> Kenneth Marshall wrote:
> >On Mon, Jan 22, 2007 at 06:42:09PM +, Simon Riggs wrote:
> >>Hold that thought! Read Heikki's Piggyback VACUUM idea on new thread...
> >
> >There may be ot
On Mon, Jan 22, 2007 at 06:42:09PM +, Simon Riggs wrote:
> On Mon, 2007-01-22 at 13:27 -0500, Bruce Momjian wrote:
> > Yep, agreed on the random I/O issue. The larger question is if you have
> > a huge table, do you care to reclaim 3% of the table size, rather than
> > just vacuum it when it g
On Thu, Jul 28, 2005 at 12:53:07AM -0400, Tom Lane wrote:
> Gregory Youngblood <[EMAIL PROTECTED]> writes:
> > ... the problem is unsigned bigint in mysql to postgresql.
> > There's not another larger integer size that can be used that would
> > allow the 18446744073709551615 (is that the max v
19 matches
Mail list logo
