Hi,
https://www.postgresql.org/docs/current/catalog-pg-class.html
relkind char
> relpersistence char
> relreplident char
these 3 columns type should be "char" ?
On 4/27/23 17:58, Michael Xu wrote:
Please reply to list also.
Ccing list.
1) Are you sure whatever client you are using is not doing
"ads.MyTableName"?
Confirm, it is not ads.MyTableName.
1) What client(and it's version) are you using?
2) What I asked was whether the schema and table
>If you're porting a bunch of code written for Oracle to Postgres,
>you'd have to run around and change every occurrence of "date" to
>"timestamp" ... unless you install orafce, in which case you can
>rely on this alias type that orafce creates. But you do then have
>two types named "date"
> On Apr 27, 2023, at 12:40 PM, Michael Xu wrote:
>
>
> Hi,
>
> By default, pgsql accepts double quotes around schema's name in a query, e.g.
> select * from "ads"."MyTableName". In our env, it throws 42P01:relation
> "ads.MyTableName" does not exist. It is okay if no double quote around
On 4/27/23 12:40, Michael Xu wrote:
Hi,
By default, pgsql accepts double quotes around schema's name in a query,
e.g. select * from "ads"."MyTableName". In our env, it throws
42P01:relation "ads.MyTableName" does not exist. It is okay if no double
quote around schema name, select * from
> On Apr 27, 2023, at 12:40, Michael Xu wrote:
> In our env, it throws 42P01:relation "ads.MyTableName" does not exist.
The function of double quotes in SQL is to allow you do include characters that
would otherwise not be legal in an identifier (as well as making the identifier
Michael Xu writes:
> By default, pgsql accepts double quotes around schema's name in a query,
> e.g. select * from "ads"."MyTableName". In our env, it throws
> 42P01:relation "ads.MyTableName" does not exist.
Works for me:
regression=# create schema ads;
CREATE SCHEMA
regression=# create table
Hi,
By default, pgsql accepts double quotes around schema's name in a query,
e.g. select * from "ads"."MyTableName". In our env, it throws
42P01:relation "ads.MyTableName" does not exist. It is okay if no double
quote around schema name, select * from ads."MyTableName".
Is there settings in
gzh writes:
> I did the following two tests and found that the return value of
> pg_catalog.date and oracle.date are inconsistent.
Yeah ... that's pretty much the point. Oracle uses the name "date"
for a data type that Postgres (and the SQL standard) calls a "timestamp".
That's very ancient
> On 27/04/2023 13:20 CEST gzh wrote:
>
> When the return type is set to oracle.date, there are hours, minutes, and
> seconds of the date value in the SQL execution result.
> Why is there such a difference and how to solve it?
orafce defines oracle.date as timestamp(0) [0] because Oracle's DATE
> On 27/04/2023 13:24 CEST Rajmohan Masa wrote:
>
> Is it possible to take differential Backup inWindows Server ?If possible
> please explain clearly?
Not to my knowledge. Postgres itself only allows full backups via pg_basebackup
or pg_dumpall.
Barman[0] allows differential backup via
PG does not have a concept of differential backup since it does not track block level changes. Pgbackrest has implemented a different backup using timestamp of last update in data files. Not sure whether it works in windows.--Sent from phone.From: Rajmohan Masa Sent: Thursday, April 27, 2023, 7:25
Hi Team,
Is it possible to take differential Backup in* Windows Server ? *If
possible please explain clearly?
I tried with different scenarios but I'm unable to take *Diff Backup* of
the postgresql database in *Windows server.*
*Much appreciated for Response.*
*Thank you,*
*Rajamohan M.*
Thank you very much for your reply.
I did the following two tests and found that the return value of
pg_catalog.date and oracle.date are inconsistent.
①the function was created with return type pg_catalog.date
---
CREATE OR REPLACE FUNCTION to_date(str text) RETURNS pg_catalog.date AS
On Thu, 2023-04-27 at 11:44 +0200, Dominique Devienne wrote:
> as someone who must store ZLIB (from ZIP files)
> and sometimes LZ4 compressed `bytea` values, I often find it's a shame that I
> have
> to decompress them, send them over the wire uncompressed, to have the
> PostgreSQL
> backend
On Thu, Apr 27, 2023 at 11:24 AM Laurenz Albe
wrote:
> On Thu, 2023-04-27 at 14:48 +0530, Tushar Takate wrote:
> > Does PostgreSQL support in-transit compression for a client connection?
>
> No, not any more.
>
On a related but different subject, as someone who must store ZLIB (from
ZIP files)
On Thu, 2023-04-27 at 14:48 +0530, Tushar Takate wrote:
> Does PostgreSQL support in-transit compression for a client connection?
No, not any more. There used to be compression via SSL, but that was
removed for security reasons, and because most binary distributions of
OpenSSL didn't support it
> On 27 Apr 2023, at 11:18, Tushar Takate wrote:
> Does PostgreSQL support in-transit compression for a client connection?
No. Earlier versions supported SSL compression for encrypted connections but
that rarely worked as it was disabled in the vast majority of all OpenSSL
installations.
Hi Team,
Does PostgreSQL support in-transit compression for a client connection?
*If yes*, Then please help me with the below.
1. 1. What are the different methods?
2. 2. How to enable/use it?
Thanks & Regards,
Tushar K Takate.
I'm using an EC2 on AWS running Amazon Linux 2. I'm trying to install
Postgresql version 15 server along with the contrib libraries for various
extension.
This is how I installed Posgres15
sudo rpm --import https://yum.postgresql.org/RPM-GPG-KEY-PGDG-15
sudo yum update -y
sudo yum install -y
20 matches
Mail list logo
