Hi,
>Are the servers on the Windows versions you mention or the clients or both?
Both clients as well as server are located on the same Windows Server machine.
>Where is this error showing up, the Windows or Postgres logs?
Both. It appears in the pg_log as well as failing the client
>What doe
On Fri, 2014-01-10 at 10:10 +0100, Rémi Cura wrote:
> Hey List,
> kind of a simple question :
>
> I'm using the postgis_topology extension,
> and I'm trying to figure where the slowness comes from when importing data.
>
> It involves plpgsql function calling other plpgsql functions, insert,
> upd
Thanks all =)
Cheers,
Rémi-C
2014/1/13 Guillaume Lelarge
> On Fri, 2014-01-10 at 10:10 +0100, Rémi Cura wrote:
> > Hey List,
> > kind of a simple question :
> >
> > I'm using the postgis_topology extension,
> > and I'm trying to figure where the slowness comes from when importing
> data.
> >
Hello Chris,
Le 2014-01-12 à 23:24, Chris Travers a écrit :
>
> On Sun, Jan 12, 2014 at 6:30 AM, François Beausoleil
> wrote:
> Hi all,
>
> I'm thinking that all apps that connect to the database should have their own
> user. For example, the web application process is one user, then a report
On Fri, Jan 10, 2014 at 11:53 AM, Adrian Klaver wrote:
> On 01/10/2014 08:40 AM, Joseph Kregloh wrote:
>
>> Just as a followup to this. The process that I am using to do the
>> upgrade is as follows:
>>
>> 1. Install Postgres 9.3 in /opt dir.
>> 2. In 9.0 instance update spclocation in pg_tablespa
Right. I know there were multiple issue with this upgrade, jails
> probably being the biggest, but a new one I had never heard is that _if_
> you are placing your tablespaces in the PGDATA directory, and you are
> upgrading from pre-9.2, if you rename the old data directory, you also
> need to sta
Hi Kevin,
Thanks for the prompt answer.
The Page 0 of the record is very much existing.
But still If take a dump of pg_largeobject_metadata from source database
still the same
message.
The database runs under the 'postgres' superuser only.
Can I recreate the pg_largeobject_metadata by which co
Hi Kevin,
>From Mr Momijan's suggestion by running the following query, I was in a
position
to create the pg_largeobject_metadata table instead of copying, I assumed
that
postgres is the user at source and hence it should work for destination
also. But
by running the following command
select
=?GB2312?B?RmVsaXgu0Ow=?= writes:
> //line 194 : In a "most common values" slot, staop is the OID of the "="
> operator used to decide whether values are the same or not.
> //line 206 : A "histogram" slot describes the distribution of scalar data.
> staop is the OID of the "<" operator that descr
I see, thanks, so columns of staop* are not currently used by the planner by
default, right?
The type of staop is oid, which table is related to it?
2014-01-13
ygnhzeus
发件人：Tom Lane
发送时间：2014-01-13 23:21
主题：Re: [GENERAL] How to specify/mock the statistic data of tables in PostgreSQL
收件人："
On 01/13/2014 01:44 AM, Abraham, Danny wrote:
Hi,
Are the servers on the Windows versions you mention or the clients or both?
Both clients as well as server are located on the same Windows Server machine.
Where is this error showing up, the Windows or Postgres logs?
Both. It appears in th
Hi,
Thanks a lot for your reply ...
>From what I can find WSACancelBlockingCall is a Winsock function has to do
>with networking/messaging and not memory issues per se. So what makes you
>think it is a memory issue >or are the memory problems a separate issue?
See below for more detail on WSA
Hello, I am in the process of planning a 9.3 migration of postgres and I am
curious about the checksum features available. In my test 9.3 instance it
seemed like this feature provides a log entry of the exact database/oid of
the corrupt object when it is accessed, but not much else. I can't find
On 01/13/2014 08:43 AM, Abraham, Danny wrote:
Hi,
Thanks a lot for your reply ...
From what I can find WSACancelBlockingCall is a Winsock function has to do with
networking/messaging and not memory issues per se. So what makes you think it is a
memory issue >or are the memory problems a sepa
Hi:
On Mon, Jan 13, 2014 at 5:26 PM, Tirthankar Barari wrote:
> On 01/10/2014 07:06 AM, Francisco Olarte wrote:
>> Not related to your vacuum problem, but if your pattern is something
>> like deleting everything inserted 15 days ago you may want to think of
>> using partitioning or simple inherit
On 01/10/2014 07:06 AM, Francisco Olarte wrote:
Hi:
On Thu, Jan 9, 2014 at 7:50 PM, Tirthankar Barari wrote:
We have a table where we insert about 10 million rows everyday. We keep 14
day's worth of entries (i.e. 140 mil). A scheduled task wakes up every day
and deletes all entries past the 14
Hi,
This is sort of a continuation of = problems I was working on last week
with selective restorations of an archive file at the schema or table level. (
V9.3)
Given that I dumped the entire database ( pg_dump -Fc my_db -f archive_file )
When I pg_restore an entire schema ( -n ) everything
On 01/13/2014 01:43 PM, Day, David wrote:
Hi,
This is sort of a continuation of = problems I was working on last week
with selective restorations of an archive file at the schema or table
level. ( V9.3)
Given that I dumped the entire database ( pg_dump –Fc my_db –f
archive_file )
When I pg_
On 01/13/2014 01:43 PM, Day, David wrote:
Hi,
This is sort of a continuation of = problems I was working on last week
with selective restorations of an archive file at the schema or table
level. ( V9.3)
Given that I dumped the entire database ( pg_dump –Fc my_db –f
archive_file )
When I pg_
On 01/13/2014 08:50 AM, Mike Broers wrote:
Hello, I am in the process of planning a 9.3 migration of postgres and I
am curious about the checksum features available. In my test 9.3
instance it seemed like this feature provides a log entry of the exact
database/oid of the corrupt object when it i
On Tue, Jan 14, 2014 at 1:50 AM, Mike Broers wrote:
> Hello, I am in the process of planning a 9.3 migration of postgres and I am
> curious about the checksum features available. In my test 9.3 instance it
> seemed like this feature provides a log entry of the exact database/oid of
> the corrupt
21 matches
Mail list logo
